From: Nicholas Nethercote <n.nethercote@gmail.com>
Date: Tue, 2 Nov 2004 09:13:12 +0000 (+0000)
Subject: clarify debugging instructions
X-Git-Tag: svn/VALGRIND_3_0_0~1406
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=d62aa78d9dcacc7fdebdf9f4f64c409a7c2189e0;p=thirdparty%2Fvalgrind.git

clarify debugging instructions


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2901
---

diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index a7fa4689c4..34fb10b0ca 100644
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -34,7 +34,9 @@ file.  Eg:
 
 Debugging Valgrind with GDB
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To debug Valgrind itself with GDB, start Valgrind like this:
+To debug stage 1 just run it under GDB in the normal way.
+
+To debug Valgrind proper (stage 2) with GDB, start Valgrind like this:
 
   valgrind --tool=none --wait-for-gdb=yes <prog>
 
@@ -47,3 +49,7 @@ you want and do this in gdb:
 
   jump *$eip
 
+Code that runs in the target program such as the pthread replacement
+code or the malloc replacement code would have to be debugged as part
+of the target program, probably by attaching a debugger after it has
+started.  We are not sure if this would work, however.