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

            Bug ID: 429424
           Summary: vex amd64->IR: unhandled instruction bytes
           Product: valgrind
           Version: unspecified
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: vex
          Assignee: jsew...@acm.org
          Reporter: okell...@users.sourceforge.net
  Target Milestone: ---

SUMMARY

vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0 0x0 0x0 0x0 0xC0 0x95
0xF0 0xC

echo 'asm(".byte 0xF0, 0xC, 0x0, 0x0, 0x0, 0x0, 0xC0, 0x95, 0xF0, 0xC");' > i.c
gcc -c i.c
objdump -d i.o

Disassembly of section .text:

0000000000000000 <.text>:
   0:   f0 0c 00                lock or $0x0,%al
   3:   00 00                   add    %al,(%rax)
   5:   00 c0                   add    %al,%al
   7:   95                      xchg   %eax,%ebp
   8:   f0                      lock
   9:   0c                      .byte 0xc

on running valgrind on self built umbrello
(https://invent.kde.org/sdk/umbrello)

STEPS TO REPRODUCE

valgrind ./umbrello/umbrello5

OBSERVED RESULT

==24798== Memcheck, a memory error detector
==24798== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==24798== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==24798== Command: ./umbrello/umbrello5
==24798== 
==24798== Conditional jump or move depends on uninitialised value(s)
==24798==    at 0x13DB3C6D: ??? (in /memfd:sljit (deleted))
==24798==    by 0x10E53477: ???
==24798== 
==24798== Conditional jump or move depends on uninitialised value(s)
==24798==    at 0x13DB3C75: ??? (in /memfd:sljit (deleted))
==24798==    by 0x11267387: ???
==24798== 
==24798== Conditional jump or move depends on uninitialised value(s)
==24798==    at 0x13DB3C75: ??? (in /memfd:sljit (deleted))
==24798==    by 0x11267387: ???
==24798==    by 0x11267387: ???
==24798==    by 0x11267397: ???
==24798==    by 0x11369B6F: ???
==24798==    by 0x11267387: ???
==24798== 
==24798== Use of uninitialised value of size 8
==24798==    at 0x13DB3E85: ??? (in /memfd:sljit (deleted))
==24798==    by 0x11267387: ???
==24798==    by 0x11267387: ???
==24798==    by 0x11267397: ???
==24798==    by 0x11369B6F: ???
==24798==    by 0x11267387: ???
==24798== 
vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0 0x0 0x0 0x0 0xC0 0x95
0xF0 0xC
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
==24798== valgrind: Unrecognised instruction at address 0x11369b72.
==24798==    at 0x11369B72: ???
==24798==    by 0x11267387: ???
==24798==    by 0x11267387: ???
==24798==    by 0x11267397: ???
==24798==    by 0x11369B6F: ???
==24798==    by 0x11267387: ???
==24798== Your program just tried to execute an instruction that Valgrind
==24798== did not recognise.  There are two possible reasons for this.
==24798== 1. Your program has a bug and erroneously jumped to a non-code
==24798==    location.  If you are running Memcheck and you just saw a
==24798==    warning about a bad jump, it's probably your program's fault.
==24798== 2. The instruction is legitimate but Valgrind doesn't handle it,
==24798==    i.e. it's Valgrind's fault.  If you think this is the case or
==24798==    you are not sure, please let us know and we'll try to fix it.
==24798== Either way, Valgrind will now raise a SIGILL signal which will
==24798== probably kill your program.
KCrash: Application 'umbrello5' crashing...


EXPECTED RESULT

No unhandled instruction bytes

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION

Tried this with SuSE provided valgrind-3.16.1 using gcc-7 and gcc-10 on:

openSUSE Tumbleweed 20201110 and older
Linux 5.9.1-2-default #1 SMP Mon Oct 26 07:02:23 UTC 2020 (435e92d) x86_64
x86_64 x86_64 GNU/Linux
AMD Athlon II X2 250

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

Reply via email to