[ltt-dev] Can I use LTTng for auto-discovery of build dependencies?

[Mathieu Desnoyers]

* vesselin kavalov (vesselin_kavalov at yahoo.com) wrote:
> I am a consultant and constantly have to deal with new environments, where I 
> have to build RTL netlists (and testbenches)? for simulation or synthesis or 
> emulation and usually these involve thousands of files, most of which are passed 
> to the corresponding EDA sw tools as search paths - in general - unknown till 
> compile/run time of that tool.
> 
> 
> I would like to be able to "snoop" on a flow and detect which executable uses 
> which files as inputs/outputs and build the dependency tree, such that can be 
> fed in some form to a make/make-like sw build tool for incremental compiles.
> 
> Most of the executables are just dynamically linked, stripped binaries, so I 
> cannot compile them with some tracing beacon in them - gotta be something that 
> runs on the side or creates a shell that intercepts syscalls like file open() 
> etc.

LTTng already traces the "open" system call from within the kernel,
along with the file names opened and it knows which thread is being
executed. So you already have all the information you need within the
LTTng kernel traces.

Thanks,

Mathieu

> 
> Any help will be greatly appreciated!
> Thanx
> vess
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev


-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com