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

diff --git a/Makefile.am b/Makefile.am
index 60252dd9602d957d5be91c33bb69e264d42ba589..80312bf119196ce0eb12e4534b25a2d7802bd03f 100644 (file)
--- 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 87c03053e8766d03f02ec4379441fffe454fed53..a7fa4689c49dedddebe766804aa81ea5d8846cd8 100644 (file)
--- 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 <prog>
+
+Then start gdb like this in another terminal:
+
+  gdb /usr/lib/valgrind/stage2 <pid>
+
+Where <pid> is the pid valgrind printed. Then set whatever breakpoints
+you want and do this in gdb:
+
+  jump *$eip
+