Summary: | vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D (adcx) | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | |
Component: | vex | Assignee: | Ivo Raisr <ivosh> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | ivosh |
Priority: | NOR | ||
Version: | 3.12 SVN | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
mail
2016-11-23 10:05:58 UTC
Please could you report which unhandled instruction is this? You can use gdb or objdump, for example. (In reply to Ivo Raisr from comment #1) > Please could you report which unhandled instruction is this? You can use gdb > or objdump, for example. Hi, Can you be more specific on how to use gdb or objdump to find the illegal instruction ? Thanks, Cyril. For example with objdump: objdump -d /home/xxxxx/lib/libgmp.so.10.3.1 | grep '66 4d 0f 38 f6 d2 66 4d' and the instruction name should be right after the byte sequence. Hope it can help :
> objdump -d libgmp.so.10.3.1 | grep '66 4d 0f 38 f6 d2'
2cac2: 66 4d 0f 38 f6 d2 adcx %r10,%r10
Cyril
Yes, it indeed does. Thank you. This bug is a duplicate of: 360415 amd64 instructions ADCX and ADOX are not implemented in VEX *** This bug has been marked as a duplicate of bug 360415 *** |