From: Nicholas Nethercote Date: Tue, 21 Mar 2006 23:15:43 +0000 (+0000) Subject: Make the unrecognised-instruction error message more informative. X-Git-Tag: svn/VALGRIND_3_2_0~173 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d1987a4b7d0c70c91db81d39c3562b97651b4e96;p=thirdparty%2Fvalgrind.git 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 b5ad40cef2..b1bc09a533 100644 --- 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