https://bugs.kde.org/show_bug.cgi?id=434057
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #1 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
Note that valgrind gdbserver is very special: it is not a 'separate' process
that e.g. do ptrace system calls to debug an inferior.
The valgrind gdbserver is embedded in valgrind itself.
Due to that, when the valgrind guest process is blocked in a syscall,
the valgrind gdbserver cannot 'read' packets from gdb.
The intermediate vgdb process is reading the packets from gdb,
and then wakes up (in a very special way) the valgrind runtime to get
the valgrind guest process out of the blocking system call.
As such, a direct connnection between gdb and the valgrind gdbserver
will not work properly.
A possible implementation might be a new vgdb option such as:
--valgrind [VALGRIND_OPTIONS ...] PROGRAM_TO_RUN_UNDER_VALGRIND [PROGRAM_ARGS
...]
When vgdb gets this argument, it would launch valgrind itself and connect to
it.
That avoids thus to have to launch valgrind in one window, and have gdb/vgdb
launched
in another window.
--
You are receiving this mail because:
You are watching all bug changes.
