| Summary: | vex amd64->IR: unhandled instruction bytes: 0xDD 0xB0 0x30 0x2 0x0 0x0 | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | shijun.wang <wangsj001> |
| Component: | bbv | Assignee: | Vince Weaver <vince> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | tom |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
*** This bug has been marked as a duplicate of bug 143325 *** |
vex amd64->IR: unhandled instruction bytes: 0xDD 0xB0 0x30 0x2 0x0 0x0 unhandled opc_aux = 0x 6 first_opcode == 0xDD vex amd64->IR: unhandled instruction bytes: 0xDD 0xB0 0x30 0x2 0x0 0x0 ==22315== valgrind: Unrecognised instruction at address 0x77ef14e. ==22315== Your program just tried to execute an instruction that Valgrind ==22315== did not recognise. There are two possible reasons for this. ==22315== 1. Your program has a bug and erroneously jumped to a non-code ==22315== location. If you are running Memcheck and you just saw a ==22315== warning about a bad jump, it's probably your program's fault. ==22315== 2. The instruction is legitimate but Valgrind doesn't handle it, ==22315== i.e. it's Valgrind's fault. If you think this is the case or I try 3.5.0-debian/ 3.6.0 /3.6.1 all failed ==22315== you are not sure, please let us know and we'll try to fix it. ==22315== Either way, Valgrind will now raise a SIGILL signal which will ==22315== probably kill your program. ==22315== #define SAVEFPU __asm("push %%rax; \ 69 mov %0, %%rax; \ 70 fsave (%%rax); \ 71 pop %%rax;"::"g"(m_FPUInfos)) fsave