From: Florian Krohm Date: Mon, 23 Jul 2012 18:05:52 +0000 (+0000) Subject: Update expected results. X-Git-Tag: svn/VALGRIND_3_8_0~92 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=068a951cf7bd5fa0b7c65a986077b1f2b241e502;p=thirdparty%2Fvalgrind.git Update expected results. This is the companion patch to VEX r2444 which backs out the special handling for the 00 opcode. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12776 --- diff --git a/none/tests/s390x/op00.stderr.exp1 b/none/tests/s390x/op00.stderr.exp1 index 73d098c308..d35d6d20d7 100644 --- a/none/tests/s390x/op00.stderr.exp1 +++ b/none/tests/s390x/op00.stderr.exp1 @@ -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) diff --git a/none/tests/s390x/op00.stderr.exp2 b/none/tests/s390x/op00.stderr.exp2 index d587a6619e..d35d6d20d7 100644 --- a/none/tests/s390x/op00.stderr.exp2 +++ b/none/tests/s390x/op00.stderr.exp2 @@ -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........ diff --git a/none/tests/s390x/op_exception.stderr.exp b/none/tests/s390x/op_exception.stderr.exp index 24c6bf30f4..c76666888f 100644 --- a/none/tests/s390x/op_exception.stderr.exp +++ b/none/tests/s390x/op_exception.stderr.exp @@ -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 @@ did not recognise. There are two possible reasons for this. 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.