So, how easy is it to debug valgrind?
Valgrind is hanging left and right for me on chromium's unit tests today.
It's quite reproducible; would running it under gdb be likely to
find out why?
I tried running valgrind in gdb by editing vg-in-place to read
VALGRIND_LIB="$vgbasedir/.in_place" \
VALGRIND_LIB_INNER="$vgbasedir/.in_place" \
gdb "$vgbasedir/coregrind/valgrind"
and then doing
set args /bin/true
run
That worked fine, but doing it with my real app blew chunks:
Program received signal SIGSEGV, Segmentation fault.
0x0b7e6cf7 in ?? ()
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
