| Summary: | vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55 | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Eric Knaak <eeknaak> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | eeknaak, tom |
| Priority: | NOR | ||
| Version: | 3.13.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Log after running autonauts in wine in valgrind
Hard_info report |
||
steam for linux version: Built: Nov 20 2019, at 01:49:33 Created attachment 124184 [details]
Hard_info report
Please give us the full error - valgrind should have reported what instruction it couldn't decode in detail before the stack trace. tried building the 32 bit binary to get 3.15 to run, but "/usr/bin/ld: i386:x86-64 architecture of input file `valgrind-m_debuglog.o' is incompatible with i386 output" instead. I'll look for help so I can see if this issue is in the 3.15 version. (In reply to Tom Hughes from comment #4) > Please give us the full error - valgrind should have reported what > instruction it couldn't decode in detail before the stack trace. The full error should be in the log file attached. Is it not in there? "Log after running autonauts in wine in valgrind" Where can I find the full error. is it in a log file somewhere? Sorry I missed that. Here are the important details: vex amd64->IR: unhandled instruction bytes: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==21781== valgrind: Unrecognised instruction at address 0x7bcb6b83. So that is IRET which is not currently supported in 64 bit mode. We already have a bug covering this so I'm going to close this as a duplicate. *** This bug has been marked as a duplicate of bug 253657 *** Hmm, IRETQ got fixed recently, bug 400538, exactly for the purposes of running Wine in 64-bit mode. It's in the trunk: git clone git://sourceware.org/git/valgrind.git But maybe I misunderstand? Ah I had a feeling it has been fixed recently but I missed that. The user here is running 3.13 so won't have the fix but I'll update the duplicate. *** This bug has been marked as a duplicate of bug 400538 *** |
Created attachment 124183 [details] Log after running autonauts in wine in valgrind SUMMARY Wine version doesn't seem to mater. Most recently I ran using wine 4.20 STEPS TO REPRODUCE 1. Install autonauts 2. tell valgrind to run autonauts. 3. get this error ==21781== valgrind: Unrecognised instruction at address 0x7bcb6b83. ==21781== at 0x7BCB6B83: ??? (in /opt/wine-devel/lib64/wine/ntdll.dll.so) OBSERVED RESULT ==21781== valgrind: Unrecognised instruction at address 0x7bcb6b83. ==21781== at 0x7BCB6B83: ??? (in /opt/wine-devel/lib64/wine/ntdll.dll.so) EXPECTED RESULT Autonauts to run normally and not crash with an error SOFTWARE/OS VERSIONS Ubuntu 18.04 Valgrind 3.13.0 wine 4.20 ADDITIONAL INFORMATION Attempted with valgrind 3.15 But I don't know how to compile it correctly. I'll add more info if I can get valgrind 3.15 running.