>From: Julian Seward [mailto:[email protected]] >You can also send output to a network socket (eg, >--log-socket=127.0.0.1:1500) >and have the valgrind-listener program listen on the socket. This is >really really useful (at least I think so :-) but nobody seems to know >it exists. > >J
Effectively, having a way to avoid mixing VG output with program output is interesting. I replicated this idea as part of the gdbserver patch: I have hooked up on the "log output sink" to allow gdb to display the VG output. However, the output_log_sink does not work for debug. From what I can see, VG_(debugLog) always goes to stderr. Philippe ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
