Bug 159720 - Opcode 0xFF 0x58 0xEB 0x5 unhandled on x86
Summary: Opcode 0xFF 0x58 0xEB 0x5 unhandled on x86
Status: REPORTED
Alias: None
Product: valgrind
Classification: Developer tools
Component: vex (show other bugs)
Version: 3.3.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks: 256630
  Show dependency tree / graph
 
Reported: 2008-03-23 00:35 UTC by Nicolas
Modified: 2010-11-11 20:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas 2008-03-23 00:35:01 UTC 
Hello,
While running qemu under Valgrind for debugging purposes, I got the message "vex
x86->IR: unhandled instruction bytes: 0xFF 0x58 0xEB 0x5". This is a valid
opcode (CALLF Ep).
I think this opcode should be implemented.
Thanks,
Nicolas
Comment 1 Julian Seward 2008-03-23 00:45:25 UTC 
> While running qemu under Valgrind for debugging purposes, I got the message


This is qemu + the qemu accelerator, yes?
Comment 2 Nicolas 2008-03-23 01:11:03 UTC 
No, it's qemu without kqemu.
Comment 3 Nicolas 2008-03-26 20:17:16 UTC 
Hi,
Did I give you enough information, or do you need more?
Thanks,
Nicolas
Comment 4 Julian Seward 2008-05-09 19:24:24 UTC 
Looking at this more.  This is a "lcall" or far call.  Do you have some
more details of it?  What arguments did you give to qemu?
Comment 5 Nicolas 2008-05-09 19:54:29 UTC 
Hi,
I have no more details on this. I don't remember the exact arguments, but it was probably something like qemu -smp 2 -cdrom KNOPPIX_V5.1.0CD-2006-12-30-EN.iso
In case it helps, it was with qemu 0.9.1.
Comment 6 Julian Seward 2008-05-11 10:28:11 UTC 
Hmm, hard to fix without a real test case.