https://bugs.kde.org/show_bug.cgi?id=510694
Bug ID: 510694
Summary: Handle qExecAndArgs remote protocol packet
Classification: Developer tools
Product: valgrind
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
If valgrind is started like this:
valgrind --tool=memcheck --vgdb=full --vgdb-stop-at=startup /path/to/prog arg1
arg2 arg3
then valgrind will start up, and prompt us to connect to the running process
like this:
(gdb) gdb /path/to/prog
target remote | /usr/bin/vgdb --pid=12345
In this case the remote target is already running. There are a couple of
things here which don't really work. The most important is
(gdb) show args
Argument list to give program being debugged when it is started is "".
If the qExecAndArgs were supported then this could potentially show the actual
argument list here. The other thing that doesn't work, is:
(gdb) show remote exec-file
which shows the empty string, with full qExecAndArgs this would show the actual
remote executable filename.
--
You are receiving this mail because:
You are watching all bug changes.
