2017-06-09 21:55 GMT+02:00 Alberthus via Valgrind-users <valgrind-users@lists.sourceforge.net>: > Hello, > I'm new to programing and have been learning how to debug my program with > gdb and find leaks with valgrind, and have been trying to do them both > together using the instructions described in section 3.2 of > http://valgrind.org/docs/manual/manual-core-adv.html > I have been having problems finishing the valgrind session, the suggestion > given by the answer at > https://stackoverflow.com/questions/37731497/quit-valgrind-cleanly-when-debugging-with-gdb, > works but is not always, is this the way it is expected we quit valgrind? > Later on I also found by typing on gdb: > (gdb)monitor help > and I found the command v.kill that also worked for me. > > I suggest that you change the manual so that it will also teach a way to > quit vgdb somewhere near where you teach how to use it, will be usefull in a > documentation
Hello Alberthus, So if I understand it correctly, you would like to see command "monitor v.kill" listed in a subsection of section "3.2. Debugging your program using Valgrind gdbserver and GDB"? For example a new subsection called "3.2.5 Disconnecting GDB from Valgrind gdbserver"? Let me know, I. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
