Hello DTracers, I am wondering whether someone is thinking about instrumenting make/dmake/gmake with DTrace probes that could fire when make selects various targets and provide some information about the target. Any interest in this area? - akolb
What do you want to find out that you couldn''t get by tracking *make and its descendant processes, down to whatever level you desire? Are there parts of *make''s "reasoning" you''d like to understand or is this just a matter of convenience? Perhaps with a use case or two to consider, folks may be able to make appropriate suggestions. -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume rdm at cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development
>>>>> "Rich" == Rich Morin <rdm at cfcl.com> writes:Rich Morin <rdm at cfcl.com> wrote: Rich> What do you want to find out that you couldn''t get by tracking Rich> *make and its descendant processes, down to whatever level you Rich> desire? Are there parts of *make''s "reasoning" you''d like to Rich> understand or is this just a matter of convenience? Rich> Perhaps with a use case or two to consider, folks may be able Rich> to make appropriate suggestions. Sure, consider this example: foo: bar cd foobar; make What I will see by looking at child processes is make in foobar. What I''d like to know is that we went there because of foo:bar dependency. Also suppose that the foo target is not rebuilt because foo is touched later than bar. We will not see any child processes for that but it would be useful to know that the target was actually considered. - akolb