1
2vex s390->IR: unknown insn: 0000
3valgrind: Unrecognised instruction at address 0x.........
4   at 0x........: main (op_exception.c:23)
5Your program just tried to execute an instruction that Valgrind
6did not recognise.  There are two possible reasons for this.
71. Your program has a bug and erroneously jumped to a non-code
8   location.  If you are running Memcheck and you just saw a
9   warning about a bad jump, it's probably your program's fault.
102. The instruction is legitimate but Valgrind doesn't handle it,
11   i.e. it's Valgrind's fault.  If you think this is the case or
12   you are not sure, please let us know and we'll try to fix it.
13Either way, Valgrind will now raise a SIGILL signal which will
14probably kill your program.
15vex s390->IR: unknown insn: 0000
16valgrind: Unrecognised instruction at address 0x.........
17   at 0x........: main (op_exception.c:23)
18Your program just tried to execute an instruction that Valgrind
19did not recognise.  There are two possible reasons for this.
201. Your program has a bug and erroneously jumped to a non-code
21   location.  If you are running Memcheck and you just saw a
22   warning about a bad jump, it's probably your program's fault.
232. The instruction is legitimate but Valgrind doesn't handle it,
24   i.e. it's Valgrind's fault.  If you think this is the case or
25   you are not sure, please let us know and we'll try to fix it.
26Either way, Valgrind will now raise a SIGILL signal which will
27probably kill your program.
28vex s390->IR: unknown insn: FFFF FFFF FFFF
29valgrind: Unrecognised instruction at address 0x.........
30   at 0x........: main (op_exception.c:30)
31Your program just tried to execute an instruction that Valgrind
32did not recognise.  There are two possible reasons for this.
331. Your program has a bug and erroneously jumped to a non-code
34   location.  If you are running Memcheck and you just saw a
35   warning about a bad jump, it's probably your program's fault.
362. The instruction is legitimate but Valgrind doesn't handle it,
37   i.e. it's Valgrind's fault.  If you think this is the case or
38   you are not sure, please let us know and we'll try to fix it.
39Either way, Valgrind will now raise a SIGILL signal which will
40probably kill your program.
41vex s390->IR: unknown insn: 0000
42valgrind: Unrecognised instruction at address 0x.........
43   at 0x........: main (op_exception.c:30)
44Your program just tried to execute an instruction that Valgrind
45did not recognise.  There are two possible reasons for this.
461. Your program has a bug and erroneously jumped to a non-code
47   location.  If you are running Memcheck and you just saw a
48   warning about a bad jump, it's probably your program's fault.
492. The instruction is legitimate but Valgrind doesn't handle it,
50   i.e. it's Valgrind's fault.  If you think this is the case or
51   you are not sure, please let us know and we'll try to fix it.
52Either way, Valgrind will now raise a SIGILL signal which will
53probably kill your program.
54
55