Print a stack trace as part of the "unhandled instruction bytes" warning.

Useful if the program in question catches signals, in which case the usual
"Process terminating..." stack trace isn't shown.  Requested by Jesse
Ruderman.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11504

diff --git a/coregrind/m_scheduler/scheduler.c b/coregrind/m_scheduler/scheduler.c
index f8f2950721c908700e99e44803db489fb88d8e3d..c95c6a30fee7e0f99d5771ef37c9b6b2dc7fc97e 100644 (file)
--- a/coregrind/m_scheduler/scheduler.c
+++ b/coregrind/m_scheduler/scheduler.c
@@ -1184,6 +1184,7 @@ VgSchedReturnCode VG_(scheduler) ( ThreadId tid )
          VG_(umsg)(
             "valgrind: Unrecognised instruction at address %#lx.\n",
             VG_(get_IP)(tid));
+         VG_(get_and_pp_StackTrace)(tid, 50);
 #define M(a) VG_(umsg)(a "\n");
    M("Your program just tried to execute an instruction that Valgrind" );
    M("did not recognise.  There are two possible reasons for this."    );