On Fri, Mar 18, 2011 at 5:23 AM, Adam Dingle <[email protected]> wrote: > ltrace is an extremely useful tool!
Glad you like it. > I find that when I'm tracing a tree of child processes using the -f option, > the following type of output (which is printed unconditionally) becomes > distracting: > [pid 6494] --- Called exec() --- > [pid 6496] --- Called exec() --- > [pid 6496] +++ exited (status 0) +++ > [pid 6495] --- SIGCHLD (Child exited) --- > [pid 6495] +++ exited (status 0) +++ > [pid 6494] --- SIGCHLD (Child exited) --- > [pid 6494] --- Called exec() --- > [pid 6499] --- Called exec() --- > [pid 6500] +++ exited (status 0) +++ > [pid 6499] +++ exited (status 0) +++ > ... > I'd like to propose that this ouput appear only when DEBUG_PROCESS is > enabled. Does this seem reasonable? There is already a patch in the official git repository that provides a flag to prevent printing signals in ltrace output. I suppose we could consider an additional patch that would conditionally silence the other output. If you submit a patch I can take a look, but I would almost certainly reject a patch that moves this output to only display when DEBUG_PROCESS is enabled. Joe _______________________________________________ Ltrace-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/ltrace-devel
