Bug 487301 - RUNNING status not included in XML output for forked children
Summary: RUNNING status not included in XML output for forked children
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (other bugs)
Version First Reported In: 3.24 GIT
Platform: Other Other
: NOR minor
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-20 22:01 UTC by Ivy Basseches
Modified: 2024-05-20 22:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Append running status to child's XML file along with preamble (1.64 KB, application/mbox)
2024-05-20 22:01 UTC, Ivy Basseches 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ivy Basseches 2024-05-20 22:01:13 UTC 
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.