https://bugs.kde.org/show_bug.cgi?id=379525
--- Comment #10 from Ivo Raisr <iv...@ivosh.net> --- I get the following error output from Valgrind run: $ ./vg-in-place --tool=none none/tests/amd64/cet_nops ==13161== Nulgrind, the minimal Valgrind tool ==13161== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote. ==13161== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info ==13161== Command: none/tests/amd64/cet_nops ==13161== start doing absolutely nothing .. vex amd64->IR: unhandled instruction bytes: 0x65 0xF 0x19 0xFF 0x66 0x65 0xF 0x19 0xFF 0xF2 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 ==13161== valgrind: Unrecognised instruction at address 0x401144. ==13161== at 0x401144: main (cet_nops.c:42) ==13161== Your program just tried to execute an instruction that Valgrind ==13161== did not recognise. There are two possible reasons for this. ==13161== 1. Your program has a bug and erroneously jumped to a non-code ==13161== location. If you are running Memcheck and you just saw a ==13161== warning about a bad jump, it's probably your program's fault. ==13161== 2. The instruction is legitimate but Valgrind doesn't handle it, ==13161== i.e. it's Valgrind's fault. If you think this is the case or ==13161== you are not sure, please let us know and we'll try to fix it. ==13161== Either way, Valgrind will now raise a SIGILL signal which will ==13161== probably kill your program. ==13161== ==13161== Process terminating with default action of signal 4 (SIGILL): dumping core ==13161== Illegal opcode at address 0x401144 ==13161== at 0x401144: main (cet_nops.c:42) ==13161== ./vg-in-place: line 29: 13161: Illegal instruction(coredump) Illegal Instruction (core dumped) ./vg-in-place --version -v valgrind-3.13.0.SVN-16420-vex-3384 $ gcc --version gcc (GCC) 5.4.0 Copyright (C) 2015 Free Software Foundation, Inc. -- You are receiving this mail because: You are watching all bug changes.
