|
From: <sv...@va...> - 2012-07-23 18:06:04
|
florian 2012-07-23 19:05:52 +0100 (Mon, 23 Jul 2012)
New Revision: 12776
Log:
Update expected results.
This is the companion patch to VEX r2444 which backs out the special
handling for the 00 opcode.
Modified files:
trunk/none/tests/s390x/op00.stderr.exp1
trunk/none/tests/s390x/op00.stderr.exp2
trunk/none/tests/s390x/op_exception.stderr.exp
Modified: trunk/none/tests/s390x/op00.stderr.exp2 (+13 -0)
===================================================================
--- trunk/none/tests/s390x/op00.stderr.exp2 2012-07-23 16:40:41 +01:00 (rev 12775)
+++ trunk/none/tests/s390x/op00.stderr.exp2 2012-07-23 19:05:52 +01:00 (rev 12776)
@@ -1,4 +1,17 @@
+vex s390->IR: unknown insn: 0000
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: main (op00.c:5)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
Process terminating with default action of signal 4 (SIGILL)
Illegal opcode at address 0x........
Modified: trunk/none/tests/s390x/op00.stderr.exp1 (+14 -0)
===================================================================
--- trunk/none/tests/s390x/op00.stderr.exp1 2012-07-23 16:40:41 +01:00 (rev 12775)
+++ trunk/none/tests/s390x/op00.stderr.exp1 2012-07-23 19:05:52 +01:00 (rev 12776)
@@ -1,5 +1,19 @@
+vex s390->IR: unknown insn: 0000
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: main (op00.c:5)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
Process terminating with default action of signal 4 (SIGILL)
+ Illegal opcode at address 0x........
at 0x........: main (op00.c:5)
Modified: trunk/none/tests/s390x/op_exception.stderr.exp (+39 -0)
===================================================================
--- trunk/none/tests/s390x/op_exception.stderr.exp 2012-07-23 16:40:41 +01:00 (rev 12775)
+++ trunk/none/tests/s390x/op_exception.stderr.exp 2012-07-23 19:05:52 +01:00 (rev 12776)
@@ -1,4 +1,30 @@
+vex s390->IR: unknown insn: 0000
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: main (op_exception.c:23)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
+vex s390->IR: unknown insn: 0000
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: main (op_exception.c:27)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
vex s390->IR: unknown insn: FFFF FFFF FFFF
valgrind: Unrecognised instruction at address 0x.........
at 0x........: main (op_exception.c:30)
@@ -12,4 +38,17 @@
you are not sure, please let us know and we'll try to fix it.
Either way, Valgrind will now raise a SIGILL signal which will
probably kill your program.
+vex s390->IR: unknown insn: 0000
+valgrind: Unrecognised instruction at address 0x.........
+ at 0x........: main (op_exception.c:34)
+Your program just tried to execute an instruction that Valgrind
+did not recognise. There are two possible reasons for this.
+1. Your program has a bug and erroneously jumped to a non-code
+ location. If you are running Memcheck and you just saw a
+ warning about a bad jump, it's probably your program's fault.
+2. The instruction is legitimate but Valgrind doesn't handle it,
+ i.e. it's Valgrind's fault. If you think this is the case or
+ you are not sure, please let us know and we'll try to fix it.
+Either way, Valgrind will now raise a SIGILL signal which will
+probably kill your program.
|