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

Add README_DEVELOPERS to the 'make dist' tarball (since it's mentioned in

Browse Source 
README), and add some instructions about attaching GDB to Valgrind itself
within it.

This fixes bug 90138.

MERGE WITH STABLE


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2738
This commit is contained in:
Nicholas Nethercote 2004-10-09 15:59:05 +00:00
parent e86e8e1216
commit 44f0b4c6d5
2 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Makefile.am
View File

@ -37,6 +37,7 @@ regtest: check
EXTRA_DIST = \
FAQ.txt \
ACKNOWLEDGEMENTS \
README_DEVELOPERS \
README_PACKAGERS \
README_MISSING_SYSCALL_OR_IOCTL TODO \
valgrind.spec.in valgrind.pc.in \

16
README_DEVELOPERS
View File

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