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

            Bug ID: 373166
           Summary: drd and helgrind will crash wth vex amd64->IR:
                    unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0
                    0x74 0x8 0x4D 0x89 0xE7
           Product: valgrind
           Version: 3.12.0
          Platform: RedHat RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: drd
          Assignee: bvanass...@acm.org
          Reporter: ntus...@yahoo.com
  Target Milestone: ---

The tests drd/tests/sem_open, sem_open2, sem_open3 and sem_open_traced all
crash with unhandled instruction error

==14999== drd, a thread error detector
==14999== Copyright (C) 2006-2015, and GNU GPL'd, by Bart Van Assche.
==14999== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==14999== Command: ./sem_open -m
==14999== 
vex amd64->IR: unhandled instruction bytes: 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8
0x4D 0x89 0xE7
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
==14999== valgrind: Unrecognised instruction at address 0x382bf0a2f0.
==14999==    at 0x382BF0A2F0: check_add_mapping (in
/lib64/tls/libpthread-2.3.4.so)
==14999==    by 0x4A14EDF: sem_open_intercept (drd_pthread_intercepts.c:1391)
==14999==    by 0x4A14EDF: sem_open (drd_pthread_intercepts.c:1398)
==14999==    by 0x400AFA: main (sem_open.c:63)
==14999== Your program just tried to execute an instruction that Valgrind
==14999== did not recognise.  There are two possible reasons for this.
==14999== 1. Your program has a bug and erroneously jumped to a non-code
==14999==    location.  If you are running Memcheck and you just saw a
==14999==    warning about a bad jump, it's probably your program's fault.
==14999== 2. The instruction is legitimate but Valgrind doesn't handle it,
==14999==    i.e. it's Valgrind's fault.  If you think this is the case or
==14999==    you are not sure, please let us know and we'll try to fix it.
==14999== Either way, Valgrind will now raise a SIGILL signal which will
==14999== probably kill your program.
==14999== 
==14999== Process terminating with default action of signal 4 (SIGILL): dumping
core
==14999==  Illegal opcode at address 0x382BF0A2F0
==14999==    at 0x382BF0A2F0: check_add_mapping (in
/lib64/tls/libpthread-2.3.4.so)
==14999==    by 0x4A14EDF: sem_open_intercept (drd_pthread_intercepts.c:1391)
==14999==    by 0x4A14EDF: sem_open (drd_pthread_intercepts.c:1398)
==14999==    by 0x400AFA: main (sem_open.c:63)
==14999== 
==14999== For counts of detected and suppressed errors, rerun with: -v
==14999== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction

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

Reply via email to