https://bugs.kde.org/show_bug.cgi?id=382998
Bug ID: 382998
Summary: xml-socket doesn't work
Product: valgrind
Version: 3.13.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: org...@gmail.com
Target Milestone: ---
$ 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).
--
You are receiving this mail because:
You are watching all bug changes.
