zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-04 02:18:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix up old stuff in README_DEVELOPERS, including VALGRINDLIB instructions.

Browse Source 
MERGED FROM CVS HEAD



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@3305
This commit is contained in:
Nicholas Nethercote 2005-03-12 16:47:07 +00:00
parent fe57f10722
commit 39fc3ebf0d
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README_DEVELOPERS
View File

@ -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.