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,](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
Thanks
Alberthus.
ps. English is not my native language, sorry for grammar mistake. Feel free to
point them out to me so I can improve.
------------------------------------------------------------------------------
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
