|
From: Matthias S. <zz...@ge...> - 2015-04-01 20:40:15
|
Am 01.04.2015 um 22:04 schrieb Philippe Waroquiers: > On Wed, 2015-04-01 at 12:37 +0200, Matthias Schwarzott wrote: >> Hi! >> >> Sometimes I want to write a core-dump of the current status when I am in >> gdb attached to valgrind. >> But the gdb-command gcore does not work with vgdb. > ? > Here is works (gdb 7.9) > (gdb) gcore > Saved corefile core.42000 > (gdb) mo h > general valgrind monitor commands: > .... > (the last command to show this gdb is connected to a V gdbsrv. Ok, I did not try again for some time. > However, it looks like the core dump might not be fully functional: > (gdb) core core.42000 > [New LWP 14340] > warning: Error reading shared library list entry at 0x2118e0 > Program terminated with signal SIGTRAP, Trace/breakpoint trap. > #0 test () at trivialleak.c:8 > 8 leak = (void*)malloc( 1 ); > (gdb) bt > #0 test () at trivialleak.c:8 > #1 0x0804840f in main () at trivialleak.c:12 > (gdb) > > > (the shared lib list entry looks bizarre to me). > >> Else I propose to add a monitor command to trigger the already >> implemented core-dump writing of valgrind. > It is intended to remove this capability to generate a core > dump from inside valgrind, as this is fragile/missing some registers > values/contains one single thread/... What does that mean for valgrind alone? Will you really remove writing core-dumps from the normal valgrind signal handlers? How should it react on signals that normally write core-dumps? Regards Matthias |