From: Nicholas Nethercote <njn@valgrind.org>
Date: Sat, 12 Mar 2005 16:47:07 +0000 (+0000)
Subject: Fix up old stuff in README_DEVELOPERS, including VALGRINDLIB instructions.
X-Git-Tag: svn/VALGRIND_3_0_0~1013
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=39fc3ebf0d6c046ef20f801f0ce4ccfd9585e741;p=thirdparty%2Fvalgrind.git

Fix up old stuff in README_DEVELOPERS, including VALGRINDLIB instructions.

MERGED FROM CVS HEAD



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

diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index 34fb10b0ca..664029c58f 100644
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -1,11 +1,12 @@
 
 Building and not installing it
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To run Valgrind without having to install it, run coregrind/valgrind (prefix
-with "sh" because it's not executable) with the --in-place=<dir> option, where
-<dir> is the root of the source tree (and must be an absolute path).  Eg:
 
-  sh ~/grind/head4/coregrind/valgrind --in-place=/homes/njn25/grind/head4
+To run Valgrind without having to install it, run coregrind/valgrind
+with the VALGRINDLIB environment variable set, where <dir> is the root
+of the source tree (and must be an absolute path).  Eg:
+
+  VALGRINDLIB=~/grind/head4/.in_place ~/grind/head4/coregrind/valgrind 
 
 This allows you to compile and run with "make" instead of "make install",
 saving you time.
@@ -49,7 +50,3 @@ 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.