https://bugs.kde.org/show_bug.cgi?id=3D388407

            Bug ID: 388407
           Summary: vex x86->IR: unhandled instruction bytes: 0x67 0xE8
                    0xAB 0x29
           Product: valgrind
           Version: 3.13.0
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: vex
          Assignee: jseward@acm.org
          Reporter: sdelang@sdelang.fr
  Target Milestone: ---

$ uname -a
Linux sdelang-arch 4.14.1-1-ck #1 SMP PREEMPT Thu Nov 23 19:51:37 CET 2017
x86_64 GNU/Linux

$ valgrind -v ./KAG
=3D=3D26570=3D=3D Memcheck, a memory error detector
=3D=3D26570=3D=3D Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward =
et al.
=3D=3D26570=3D=3D Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyr=
ight info
=3D=3D26570=3D=3D Command: ./KAG
...
vex x86->IR: unhandled instruction bytes: 0x67 0xE8 0xAB 0x29
=3D=3D26570=3D=3D valgrind: Unrecognised instruction at address 0x4fae45f.
=3D=3D26570=3D=3D    at 0x4FAE45F: ??? (in /usr/lib32/libGLdispatch.so.0.0.=
0)
=3D=3D26570=3D=3D    by 0x400F8EA: call_init.part.0 (in /usr/lib32/ld-2.26.=
so)
=3D=3D26570=3D=3D    by 0x400F9F6: _dl_init (in /usr/lib32/ld-2.26.so)
=3D=3D26570=3D=3D    by 0x4000C9E: ??? (in /usr/lib32/ld-2.26.so)
=3D=3D26570=3D=3D Your program just tried to execute an instruction that Va=
lgrind
=3D=3D26570=3D=3D did not recognise.  There are two possible reasons for th=
is.
=3D=3D26570=3D=3D 1. Your program has a bug and erroneously jumped to a non=
-code
=3D=3D26570=3D=3D    location.  If you are running Memcheck and you just sa=
w a
=3D=3D26570=3D=3D    warning about a bad jump, it's probably your program's=
 fault.
=3D=3D26570=3D=3D 2. The instruction is legitimate but Valgrind doesn't han=
dle it,
=3D=3D26570=3D=3D    i.e. it's Valgrind's fault.  If you think this is the =
case or
=3D=3D26570=3D=3D    you are not sure, please let us know and we'll try to =
fix it.
=3D=3D26570=3D=3D Either way, Valgrind will now raise a SIGILL signal which=
 will
=3D=3D26570=3D=3D probably kill your program.
=3D=3D26570=3D=3D=20
=3D=3D26570=3D=3D Process terminating with default action of signal 4 (SIGI=
LL): dumping
core
=3D=3D26570=3D=3D  Illegal opcode at address 0x4FAE45F
=3D=3D26570=3D=3D    at 0x4FAE45F: ??? (in /usr/lib32/libGLdispatch.so.0.0.=
0)
=3D=3D26570=3D=3D    by 0x400F8EA: call_init.part.0 (in /usr/lib32/ld-2.26.=
so)
=3D=3D26570=3D=3D    by 0x400F9F6: _dl_init (in /usr/lib32/ld-2.26.so)
=3D=3D26570=3D=3D    by 0x4000C9E: ??? (in /usr/lib32/ld-2.26.so)
--26570-- REDIR: 0x4dfee80 (libc.so.6:free) redirected to 0x48306b0 (free)
=3D=3D26570=3D=3D=20
=3D=3D26570=3D=3D HEAP SUMMARY:
=3D=3D26570=3D=3D     in use at exit: 10,356 bytes in 6 blocks
=3D=3D26570=3D=3D   total heap usage: 6 allocs, 0 frees, 10,356 bytes alloc=
ated
=3D=3D26570=3D=3D=20
=3D=3D26570=3D=3D Searching for pointers to 6 not-freed blocks
=3D=3D26570=3D=3D Checked 473,192 bytes
=3D=3D26570=3D=3D=20
=3D=3D26570=3D=3D LEAK SUMMARY:
=3D=3D26570=3D=3D    definitely lost: 0 bytes in 0 blocks
=3D=3D26570=3D=3D    indirectly lost: 0 bytes in 0 blocks
=3D=3D26570=3D=3D      possibly lost: 0 bytes in 0 blocks
=3D=3D26570=3D=3D    still reachable: 10,356 bytes in 6 blocks
=3D=3D26570=3D=3D         suppressed: 0 bytes in 0 blocks
=3D=3D26570=3D=3D Rerun with --leak-check=3Dfull to see details of leaked m=
emory
=3D=3D26570=3D=3D=20
=3D=3D26570=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 fr=
om 0)
=3D=3D26570=3D=3D ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 fr=
om 0)
[1]    26570 illegal hardware instruction (core dumped)  valgrind -v ./KAG

Using lib32-mesa 17.3.1-2 from arch repos.
Using nouveau, lib32-libglvnd 1.0.0-1, linux-ck built as of Linux 4.14.1 if=
 it
helps with anything.

This is the software reproducing the issue: https://kag2d.com/en/download.
I can try to make a minimal program reproducing the issue if you desire, bu=
t I
would be unsurprised if it affected all x86 OpenGL programs with that setup.

Thanks in advance, valgrind is wonderful software :)

--=20
You are receiving this mail because:
You are watching all bug changes.=