https://bugs.kde.org/show_bug.cgi?id=510694
Mark Wielaard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|REPORTED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Mark Wielaard <[email protected]> --- (In reply to Alexandra Hajkova from comment #3) > Created attachment 186003 [details] > patch > > v2: - use handle_query.qExecAndArgs in VG_(malloc) Thanks for the update. We discussed and tested on irc. I have pushed this so it gets into v3.26.0. It nicely complements the vgdb implementation. But now it also works (with latest gdb trunk) for the traditional target remote. commit f80358f109d1bce25d2013579e5d4b933b502797 Author: Alexandra Hájková <[email protected]> Date: Wed Oct 15 06:27:25 2025 -0400 server.c: handle qExecAndArgs remote protocol packet New qExecAndArgs packet has been added recently to GDB's remote protocol. The new qExecAndArgs packet is sent from GDB, and gdbserver replies with a packet that includes the executable filename and the arguments string that were used for starting the initial inferior. On the GDB side this information can be used to update GDB's state, the 'show remote exec-file' will reflect how gdbserver was started, and 'show args' will reflect the arguments used for starting the inferior. When running valgrind together with GDB like this: ./vg-in-place --tool=memcheck --vgdb-error=0 /bin/ls -lh ~/build/gdb/gdb/gdb target remote | coregrind/vgdb We can now ask GDB to show the executable's arguments: (gdb) show args Argument list to give program being debugged when it is started is "-lh". or the executable's name: (gdb) show remote exec-file The remote exec-file is "/bin/ls". -- You are receiving this mail because: You are watching all bug changes.
