On Sat, 2024-07-20 at 10:41 -0700, Tsiang Elaine Reisler wrote: > > > I agree there is no interaction in how I am using valgrind (see last > post), but not knowing this before prompted me to ask the question on > this list. I did not use --vgd-stop-at or setup --multi mode of > interacting with gdbserver via gdb. Nevertheless, 'target remote | > vgdb' is equivalent to attaching to the process in gdb, allowing full > debugging, though without the vgdb commands (v.clo, v.info etc). These > queries elicit no response presumably because valgrind-monitor.py is > missing from gdb. The gdb python commands only provide an easier way to use the valgrind monitor commands. But if the python code is not loaded, monitor commands can still be used (but of course prefixed then with the "monitor" gdb command and not using any of the functionalities that the python layer provides).
Note that monitor command output can be either output to the gdb console or to the output of the process. So, you might check both to be sure. > > If you vgdb v.kill the valgrind process, can you and how, get a final > detail report of all the errors which is generated when the process > terminates "normally"? Kill the process really means kill the process, without giving any chance to let it run more (including to process errors). If you really need to kill your process but you want to see the errors, then in memcheck, you should launch a leak search. And then in all other tools, you can use a monitor command to list the already found errors. Philippe _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
