|
From: Philippe W. <phi...@sk...> - 2015-04-01 21:03:11
|
On Wed, 2015-04-01 at 22:40 +0200, Matthias Schwarzott wrote: > > (the last command to show this gdb is connected to a V gdbsrv. > Ok, I did not try again for some time. Testing/validation/bug reports (and bug fixes if needed) welcome :). > >> 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? Ouch, no. I confused 2 pieces of code. > How should it react on signals that normally write core-dumps? It will continue to core dump as of today, because this core dump code will stay :). Philippe |