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

            Bug ID: 393351
           Summary: unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F
                    0xD 0xE1 0xEC 0x8 0x0
           Product: valgrind
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: jsew...@acm.org
          Reporter: bvanass...@acm.org
  Target Milestone: ---

With the latest git version of fio, the latest git version of Valgrind and gcc
version 7.3.1 I encountered the following:

$ ~bart/software/valgrind/vg-in-place ~bart/software/fio/fio --name=sata
--filename=/dev/sdc --ioengine=libaio --ioscheduler=none --rw=randread
--offset=200G --size=200G --direct=1 --thread=1 --iodepth=64 --norandommap=1
==25027== Memcheck, a memory error detector
==25027== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==25027== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright
info
[ ... ]
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x48 0x6F 0xD 0xE1
0xEC 0x8 0x0
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
==25027== valgrind: Unrecognised instruction at address 0x40f695.
==25027==    at 0x40F695: fio_client_hash_init (client.c:94)
==25027==    by 0x48D48C: __libc_csu_init (elf-init.c:88)
==25027==    by 0x5E5DA17: (below main) (in /lib64/libc-2.27.so)
==25027== Your program just tried to execute an instruction that Valgrind
==25027== did not recognise.  There are two possible reasons for this.
==25027== 1. Your program has a bug and erroneously jumped to a non-code
==25027==    location.  If you are running Memcheck and you just saw a
==25027==    warning about a bad jump, it's probably your program's fault.
==25027== 2. The instruction is legitimate but Valgrind doesn't handle it,
==25027==    i.e. it's Valgrind's fault.  If you think this is the case or
==25027==    you are not sure, please let us know and we'll try to fix it.
==25027== Either way, Valgrind will now raise a SIGILL signal which will
==25027== probably kill your program.
==25027== 
==25027== Process terminating with default action of signal 4 (SIGILL): dumping
core
==25027==  Illegal opcode at address 0x40F695
==25027==    at 0x40F695: fio_client_hash_init (client.c:94)
==25027==    by 0x48D48C: __libc_csu_init (elf-init.c:88)
==25027==    by 0x5E5DA17: (below main) (in /lib64/libc-2.27.so)

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

Reply via email to