| Summary: | RUNNING status not included in XML output for forked children | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Ivy Basseches <imb2139> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | REPORTED --- | ||
| Severity: | minor | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.24 GIT | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Append running status to child's XML file along with preamble | ||
Created attachment 169670 [details] Append running status to child's XML file along with preamble SUMMARY When outputting XML of child processes to different destinations (e.g., using --xml-file=%p.xml), children do not get a RUNNING status (appending the RUNNING status is handled elsewhere in the code than the rest of the preamble). STEPS TO REPRODUCE Write and compile a program (test.c) that forks, and run it with Memcheck, outputting info to separate XML files: valgrind --leak-check=yes --xml=yes --xml-file=test-%p.xml ./test OBSERVED RESULT Child's XML output contains a FINISHED status but not a RUNNING status. EXPECTED RESULT Running status appended to child's XML output after fork.