Bug 394903 - vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0x1B 0xDA
Summary: vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0x1B 0xDA
Status: RESOLVED DUPLICATE of bug 384230
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: 3.13.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-31 19:23 UTC by Alex Henrie
Modified: 2018-09-03 07:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Henrie 2018-05-31 19:23:07 UTC 
Valgrind will not run a locally compiled copy of Wine on Arch Linux. Strangely, Valgrind does work with the Wine from the package manager, and Wine compiled on Ubuntu is also OK. The problem may be related to Bug 384156.

To reproduce, run the following commands:

git clone git://source.winehq.org/git/wine.git
cd wine
./configure
make
valgrind --trace-children=yes ./wine notepad

Result:

vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0x1B 0xDA
==20705== valgrind: Unrecognised instruction at address 0x5ea1d3f.
==20705==    at 0x5EA1D3F: ??? (in /usr/lib32/libglib-2.0.so.0.5600.0)
==20705==    by 0x400F902: call_init.part.0 (in /usr/lib32/ld-2.27.so)
==20705==    by 0x400FA01: _dl_init (in /usr/lib32/ld-2.27.so)
==20705==    by 0x401384F: dl_open_worker (in /usr/lib32/ld-2.27.so)
==20705==    by 0x4387699: _dl_catch_exception (in /usr/lib32/libc-2.27.so)
==20705==    by 0x40130E5: _dl_open (in /usr/lib32/ld-2.27.so)
==20705==    by 0x442EC62: ??? (in /usr/lib32/libdl-2.27.so)
==20705==    by 0x4387699: _dl_catch_exception (in /usr/lib32/libc-2.27.so)
==20705==    by 0x438772F: _dl_catch_error (in /usr/lib32/libc-2.27.so)
==20705==    by 0x442F400: ??? (in /usr/lib32/libdl-2.27.so)
==20705==    by 0x442ED05: dlopen (in /usr/lib32/libdl-2.27.so)
==20705==    by 0x4044774: wine_dlopen (loader.c:1041)
Comment 1 Julian Seward 2018-09-03 07:05:01 UTC 
A fix for this was landed on 2018-03-16.
See https://bugs.kde.org/show_bug.cgi?id=384230#c8

*** This bug has been marked as a duplicate of bug 384230 ***