|
From: <sv...@va...> - 2016-11-27 10:25:23
|
Author: philippe
Date: Sun Nov 27 10:25:15 2016
New Revision: 16157
Log:
Ensure the 'too early msg to use vgdb stop at valgrind abnormal exit' is produced
For this, we must directly check the command line option, as
the VG_(gdbserver_stop_at) function returns False if the gdbserver
is not yet initialised
Modified:
trunk/coregrind/m_libcassert.c
Modified: trunk/coregrind/m_libcassert.c
==============================================================================
--- trunk/coregrind/m_libcassert.c (original)
+++ trunk/coregrind/m_libcassert.c Sun Nov 27 10:25:15 2016
@@ -264,13 +264,14 @@
if (gdbserver_call_allowed && !exit_called) {
const ThreadId atid = 1; // Arbitrary tid used to call/terminate gdbsrv.
exit_called = True;
- if (status != 0 && VG_(gdbserver_stop_at) (VgdbStopAt_ValgrindAbExit)) {
+ if (status != 0
+ && VgdbStopAtiS(VgdbStopAt_ValgrindAbExit, VG_(clo_vgdb_stop_at))) {
if (VG_(gdbserver_init_done)()) {
VG_(umsg)("(action at valgrind abnormal exit) vgdb me ... \n");
VG_(gdbserver) (atid);
} else {
- VG_(umsg)("(action at valgrind abnormal exit) "
- "Early valgrind exit : vgdb not yet usable\n");
+ VG_(umsg)("(action at valgrind abnormal exit)\n"
+ "valgrind exit is too early => vgdb not yet usable\n");
}
}
if (VG_(gdbserver_init_done)()) {
|