Bug 382998 - xml-socket doesn't work
Summary: xml-socket doesn't work
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.14 SVN
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Ivo Raisr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-01 13:00 UTC by Orgad Shaneh
Modified: 2017-08-03 05:22 UTC (History)
2 users (show)

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

Attachments
Fix xml-socket issue (486 bytes, patch)
2017-08-01 17:49 UTC, Orgad Shaneh 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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.