Bug 382998

Summary: xml-socket doesn't work
Product: [Developer tools] valgrind Reporter: Orgad Shaneh <orgads>
Component: generalAssignee: Ivo Raisr <ivosh>
Status: RESOLVED FIXED    
Severity: normal CC: ivosh, orgads
Priority: NOR    
Version First Reported In: 3.14 SVN   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Fix xml-socket issue

Description Orgad Shaneh 2017-08-01 13:00:46 UTC 
$ nc -l -p 20000 &
[1] 2811
$ valgrind --xml-socket=127.0.0.1:20000 --xml=yes true 
valgrind: Bad option: --xml=yes, but no XML destination specified
valgrind: --xml=yes has been specified, but there is no XML output
valgrind: destination.  You must specify an XML output destination
valgrind: using --xml-fd, --xml-file or --xml-socket.
valgrind: Use --help for more information or consult the user manual.
[1]+  Done                    nc -l -p 20000

It looks like valgrind does connect to the socket, but closes it immediately (netcat quits after valgrind is executed).
Comment 1 Orgad Shaneh 2017-08-01 17:49:46 UTC 
Created attachment 107013 [details]
Fix xml-socket issue

The attached patch fixes this issue. Too bad this has never been tested...
Comment 2 Ivo Raisr 2017-08-03 05:22:34 UTC 
Thank you for the patch.
Fixed in SVN commit r16467.