Make the unrecognised-instruction error message more informative.

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

diff --git a/coregrind/m_scheduler/scheduler.c b/coregrind/m_scheduler/scheduler.c
index b5ad40cef23e204f9fb07fc5ead5db134b2889ed..b1bc09a533e792b6357533815e68b0291f43d451 100644 (file)
--- a/coregrind/m_scheduler/scheduler.c
+++ b/coregrind/m_scheduler/scheduler.c
@@ -955,6 +955,8 @@ VgSchedReturnCode VG_(scheduler) ( ThreadId tid )
          break;
 
       case VEX_TRC_JMP_NODECODE:
+   VG_(message)(Vg_UserMsg,
+      "valgrind: Unrecognised instruction at address %p.", VG_(get_IP)(tid));
 #define M(a) VG_(message)(Vg_UserMsg, a);
    M("Your program just tried to execute an instruction that Valgrind" );
    M("did not recognise.  There are two possible reasons for this."    );
@@ -963,7 +965,7 @@ VgSchedReturnCode VG_(scheduler) ( ThreadId tid )
    M("   warning about a bad jump, it's probably your program's fault.");
    M("2. The instruction is legitimate but Valgrind doesn't handle it,");
    M("   i.e. it's Valgrind's fault.  If you think this is the case or");
-   M("   you are not sure, please let us know."                        );
+   M("   you are not sure, please let us know and we'll try to fix it.");
    M("Either way, Valgrind will now raise a SIGILL signal which will"  );
    M("probably kill your program."                                     );
 #undef M