|
From: <sv...@va...> - 2011-10-03 17:00:11
|
Author: florian Date: 2011-10-03 17:55:26 +0100 (Mon, 03 Oct 2011) New Revision: 12088 Log: Update names of vgdb pipes in documentation. Followup to r12071. Modified: trunk/coregrind/m_gdbserver/README_DEVELOPERS Modified: trunk/coregrind/m_gdbserver/README_DEVELOPERS =================================================================== --- trunk/coregrind/m_gdbserver/README_DEVELOPERS 2011-10-03 16:15:16 UTC (rev 12087) +++ trunk/coregrind/m_gdbserver/README_DEVELOPERS 2011-10-03 16:55:26 UTC (rev 12088) @@ -125,17 +125,18 @@ How is the Valgrind gdbserver receiving commands/packets from gdb ? ------------------------------------------------------------------- The embedded gdbserver reads gdb commands on a named pipe having -(by default) the name /tmp/vgdb-pipe-from-vgdb-to-%d -where %d will be replaced by the pid. +(by default) the name /tmp/vgdb-pipe-from-vgdb-to-PID-by-USER-on-HOST +where PID, USER, and HOST will be replaced by the actual pid, the user id, +and the host name, respectively. The embedded gdbserver will reply to gdb commands on a named pipe -/tmp/vgdb-pipe-to-vgdb-from-%d +/tmp/vgdb-pipe-to-vgdb-from-PID-by-USER-on-HOST gdb does not speak directly with gdbserver in valgrind: a relay application called vgdb is needed between gdb and the valgrind-ified process. gdb writes commands on the stdin of vgdb. vgdb reads these -commands and writes them on FIFO /tmp/vgdb-pipe-from-vgdb-to-%d. -vgdb reads replies on FIFO /tmp/vgdb-pipe-to-vgdb-from-%d and writes -them on its stdout. +commands and writes them on FIFO /tmp/vgdb-pipe-from-vgdb-to-PID-by-USER-on-HOST. +vgdb reads replies on FIFO /tmp/vgdb-pipe-to-vgdb-from-PID-by-USER-on-HOST +and writes them on its stdout. Note: The solution of named pipes was preferred to tcp ip connections as it allows a discovery of which valgrind-ified processes are ready to accept |