|
From: <sv...@va...> - 2006-03-21 23:15:50
|
Author: njn
Date: 2006-03-21 23:15:43 +0000 (Tue, 21 Mar 2006)
New Revision: 5786
Log:
Make the unrecognised-instruction error message more informative.
Modified:
trunk/coregrind/m_scheduler/scheduler.c
Modified: trunk/coregrind/m_scheduler/scheduler.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/coregrind/m_scheduler/scheduler.c 2006-03-21 10:58:35 UTC (rev =
5785)
+++ trunk/coregrind/m_scheduler/scheduler.c 2006-03-21 23:15:43 UTC (rev =
5786)
@@ -955,6 +955,8 @@
break;
=20
case VEX_TRC_JMP_NODECODE:
+ VG_(message)(Vg_UserMsg,
+ "valgrind: Unrecognised instruction at address %p.", VG_(get_IP)(t=
id));
#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 @@
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
|