| Summary: | --log-file and --xml-file dont work well with --trace-children=yes | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Christian Borntraeger <borntraeger> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | mark |
| Priority: | NOR | ||
| Version: | 3.6 SVN | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | sample script that misbehaves with valgrind --trace-children=yes --log-file=... | ||
Hi Christian, I think this is a dup of https://bugs.kde.org/show_bug.cgi?id=162848 See my recent comment there - we've already fixed that in valgrind-variant, you may give it a try. *** This bug has been marked as a duplicate of bug 162848 *** |
Created attachment 52230 [details] sample script that misbehaves with valgrind --trace-children=yes --log-file=... Version: 3.6 SVN OS: Linux --log-file and --xml-file blindly create (or overwrite) the existing file. This is usually ok, but will fail with --trace-children=yes in two ways: 1. only a subset or nothing is logged 2. if the program changes into a non-writable directory the child program isnt executed at all I attached a simple shell script that behaves differently under valgrind. I am willing to fix this but I am not really sure what is the best way: 1. disallow --log-file and --xml-file with --trace-children 2. pass the file descriptor somehow to the children 3. any other idea Reproducible: Always Credits: This was found during system test on s390x by Stefan Wild.