|
From: Julian S. <js...@ac...> - 2005-11-15 11:33:09
|
On Tuesday 15 November 2005 11:07, Tom Hughes wrote: > In message <200...@cn...> > > Yao Qi <qiy...@cn...> wrote: > > The part about debugging Valgrind in README_DEVELOPERS is out-of-date. > > I code a patch for this. > > I actually think we should drop all that - there are much easier ways > to debug valgrind now that everything is statically linked with the > tool: > > - Set VALGRIND_LAUNCHER to <prefix>/bin/valgrind > > - Run "gdb <prefix>/lib/valgrind/<platform>/<tool>" > > - Do "handle SIGSEGV nostop noprint" to stop gdb stopping on > a SEGV as valgrindd needs to be able to handle them to do > stack extension > > - Set any breakpoints you want and proceed as normal for gdb That does sound like a much better way, yes. Although you need to give --tool= as an explicit arg, else it tries to load the wrong vgpreload_tool.so. Apart from that it seems to work. J |