Test 1: PASS Test 2: PASS Test 3: PASS Test 4: PASS Test 5: vex x86->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ Your program just tried to execute an instruction that Valgrind did not recognise. This might be because your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck, you might have just seen a warning about a bad jump, which is a good indication that this is so. Or it might be because the instruction is unimplemented in Valgrind; if you think this is the case, or you are not sure, please let us know. FAIL: expected si_code==2, not 1 Test 6: vex x86->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ Your program just tried to execute an instruction that Valgrind did not recognise. This might be because your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck, you might have just seen a warning about a bad jump, which is a good indication that this is so. Or it might be because the instruction is unimplemented in Valgrind; if you think this is the case, or you are not sure, please let us know. FAIL: expected signal 5, not 4 Test 7: vex x86->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ Your program just tried to execute an instruction that Valgrind did not recognise. This might be because your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck, you might have just seen a warning about a bad jump, which is a good indication that this is so. Or it might be because the instruction is unimplemented in Valgrind; if you think this is the case, or you are not sure, please let us know. FAIL: expected signal 11, not 4 Test 8: vex x86->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ Your program just tried to execute an instruction that Valgrind did not recognise. This might be because your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck, you might have just seen a warning about a bad jump, which is a good indication that this is so. Or it might be because the instruction is unimplemented in Valgrind; if you think this is the case, or you are not sure, please let us know. FAIL: expected signal 11, not 4 Test 9: vex x86->IR: unhandled instruction bytes: 0x........ 0x........ 0x........ 0x........ Your program just tried to execute an instruction that Valgrind did not recognise. This might be because your program has a bug and erroneously jumped to a non-code location. If you are running Memcheck, you might have just seen a warning about a bad jump, which is a good indication that this is so. Or it might be because the instruction is unimplemented in Valgrind; if you think this is the case, or you are not sure, please let us know. FAIL: expected signal 11, not 4