| Summary: | give more control over what is traced by --trace-children | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Bill Hoffman <bill.hoffman> |
| Component: | general | Assignee: | Nicholas Nethercote <njn> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | jseward, kdebugzilla, njn |
| Priority: | NOR | ||
| Version First Reported In: | 3.2.3 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
add --trace-children-skip option
path, updated to curr trunk, & supporting darwin/aix5 execve too patch, updated to allow use of ? and * wildcards |
||
|
Description
Bill Hoffman
2007-08-17 16:05:34 UTC
Created attachment 21422 [details]
add --trace-children-skip option
To be more flexible, it might be better to search for the string after the last / in the program being run. Then use that in the search as well. So, you don't have to list the full path to the program you don't want traced. Something like this:
Char* program = VG_(strrchr)((Char*)ARG1, '/');
if(program) program++; // move to first char past /
VG_(message)(Vg_UserMsg, "program %s %s \n", ARG1, program);
if(VG_(strstr)(VG_(clo_trace_children_skip), (Char*)ARG1)||
program && VG_(strstr)(VG_(clo_trace_children_skip), program)) {
I wrote a design proposal for this here, which drew some comments: http://blog.mozilla.com/nnethercote/2009/04/30/making-valgrind-easier-to-use-with-multi-process-programs/ *** Bug 143820 has been marked as a duplicate of this bug. *** Created attachment 36928 [details]
path, updated to curr trunk, & supporting darwin/aix5 execve too
Would also like to change it so that the strings specified
by --trace-children-skip are regexps, not complete paths.
Created attachment 36931 [details]
patch, updated to allow use of ? and * wildcards
Committed as r10927. Thanks. |