https://bugs.kde.org/show_bug.cgi?id=450458
Bug ID: 450458
Summary: unhandled instruction bytes: 0x37 0x48 0x83 0xF8 0x2E
0xF 0x84
Product: valgrind
Version: 3.19 GIT
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
When I run my application (which uses Qt) where the Qt libs were compiled with
some newer compiler
(>= clang++-9 or >= g++-9 but I'm not sure which version still did work),
then valgrind terminates with
vex amd64->IR: unhandled instruction bytes: 0x37 0x48 0x83 0xF8 0x2E 0xF 0x84
0x17 0xFF 0xFF
vex amd64->IR: REX=0 REX.W=0 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
==19360== valgrind: Unrecognised instruction at address 0x2bf6ede1.
When I run it with Qt libs compiled with older compiler (whatever was current
at around 23.Nov 2020 on openSuse TW), valgrind works just fine.
It seems newer compilers create some code valgrind can not handle yet.
Maybe there is any workaround or compiler flag I could use to prevent the
problem ?
--
You are receiving this mail because:
You are watching all bug changes.
