From 58825824520e49848ae03b3b040f65ee5437dd12 Mon Sep 17 00:00:00 2001 From: Nicholas Nethercote Date: Sat, 9 Oct 2004 16:00:58 +0000 Subject: [PATCH] Add README_DEVELOPERS to the 'make dist' tarball (since it's mentioned in README), and add some instructions about attaching GDB to Valgrind itself within it. This fixes bug 90138. MERGED FROM HEAD git-svn-id: svn://svn.valgrind.org/valgrind/branches/VALGRIND_2_2_0_BRANCH@2739 --- Makefile.am | 1 + README_DEVELOPERS | 16 ++++++++++++++++ 2 files changed, 17 insertions(+) diff --git a/Makefile.am b/Makefile.am index 60252dd960..80312bf119 100644 --- a/Makefile.am +++ b/Makefile.am @@ -42,6 +42,7 @@ regtest: check EXTRA_DIST = \ FAQ.txt \ ACKNOWLEDGEMENTS \ + README_DEVELOPERS \ README_PACKAGERS \ README_MISSING_SYSCALL_OR_IOCTL TODO \ valgrind.spec.in valgrind.pc.in diff --git a/README_DEVELOPERS b/README_DEVELOPERS index 87c03053e8..a7fa4689c4 100644 --- a/README_DEVELOPERS +++ b/README_DEVELOPERS @@ -31,3 +31,19 @@ file. Eg: perl tests/vg_regtest memcheck/tests/badfree.vgtest perl tests/vg_regtest memcheck/tests/badfree + +Debugging Valgrind with GDB +~~~~~~~~~~~~~~~~~~~~~~~~~~~ +To debug Valgrind itself with GDB, start Valgrind like this: + + valgrind --tool=none --wait-for-gdb=yes + +Then start gdb like this in another terminal: + + gdb /usr/lib/valgrind/stage2 + +Where is the pid valgrind printed. Then set whatever breakpoints +you want and do this in gdb: + + jump *$eip + -- 2.47.2