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

Extra info about debugging with GDB

Browse Source 
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6854
This commit is contained in:
Nicholas Nethercote 2007-09-17 22:35:57 +00:00
parent c7a4bb81a5
commit 86b2e5ec21
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README_DEVELOPERS
View File

@ -67,13 +67,21 @@ Debugging the main body of the valgrind code (and/or the code for
a particular tool) requires a bit more trickery but can be achieved
without too much problem by following these steps:
(1) Set VALGRIND_LAUNCHER to <prefix>/bin/valgrind:
(1) Set VALGRIND_LAUNCHER to point to the valgrind executable. Eg:
export VALGRIND_LAUNCHER=/usr/local/bin/valgrind
export VALGRIND_LAUNCHER=/usr/local/bin/valgrind
(2) Run "gdb <prefix>/lib/valgrind/<platform>/<tool>":
or for an uninstalled version in a source directory $DIR:
gdb /usr/local/lib/valgrind/ppc32-linux/lackey
export VALGRIND_LAUNCHER=$DIR/coregrind/valgrind
(2) Run gdb on the tool executable. Eg:
gdb /usr/local/lib/valgrind/ppc32-linux/lackey
or
gdb $DIR/.in_place/x86-linux/memcheck
(3) Do "handle SIGSEGV SIGILL nostop noprint" in GDB to prevent GDB from
stopping on a SIGSEGV or SIGILL:
@ -90,6 +98,8 @@ without too much problem by following these steps:
(gdb) run pwd
Steps (1)--(3) can be put in a .gdbinit file, but any directory names must
be fully expanded (ie. not an environment variable).
Self-hosting
~~~~~~~~~~~~