https://bugs.kde.org/show_bug.cgi?id=360415
Ivo Raisr <iv...@ivosh.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iv...@ivosh.net
--- Comment #16 from Ivo Raisr <iv...@ivosh.net> ---
Running the latest Valgrind on regression test fb_test_amd64 built with gcc
5.4.0 gives the following crash:
vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xC5 0x9C
0x58 0x48 0x83
vex amd64->IR: REX=1 REX.W=1 REX.R=1 REX.X=0 REX.B=1
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F38
vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0
==1119== valgrind: Unrecognised instruction at address 0x409768.
==1119== at 0x409768: exec_adcx (fb_test_amd64.h:69)
==1119== by 0x409806: test_adcx (fb_test_amd64.h:166)
==1119== by 0x411652: main (fb_test_amd64.c:1201)
Disassembly indeed shows it is adcx:
0x0000000000409767 <+405>: popfq
=> 0x0000000000409768 <+406>: adcx %r13,%r8
0x000000000040976e <+412>: pushfq
(gdb) x/16xb 0x409768
0x409768 <exec_adcx+406>: 0x66 0x4d 0x0f 0x38 0xf6 0xc5
0x9c 0x58
0x409770 <exec_adcx+414>: 0x48 0x83 0xec 0x08 0x25 0xd5
0x08 0x00
./vg-in-place --version -v
valgrind-3.13.0.SVN-16374-vex-3369
Is it possible that some paths in adcx decoding are not handled properly?
--
You are receiving this mail because:
You are watching all bug changes.
