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

            Bug ID: 365325
           Summary: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x6
                    0xF 0x42 0xC1
           Product: valgrind
           Version: 3.11.0
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: callgrind
          Assignee: josef.weidendor...@gmx.de
          Reporter: k...@kinomoto.me

==15073== Callgrind, a call-graph generating cache profiler
==15073== Copyright (C) 2002-2015, and GNU GPL'd, by Josef Weidendorfer et al.
==15073== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
----
==15073== 
==15073== For interactive control, run 'callgrind_control -h'.
vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x6 0xF 0x42
0xC1
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=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==15073== valgrind: Unrecognised instruction at address 0x512fc65.
==15073==    at 0x512FC65: std::(anonymous namespace)::__x86_rdrand()
(random.cc:69)
==15073==    by 0x512FE01: std::random_device::_M_getval() (random.cc:130)
==15073==    by 0x40659B: std::random_device::operator()() (random.h:1612)
==15073==    by 0x405ECE: __static_initialization_and_destruction_0(int, int)
(socket.cpp:26)
==15073==    by 0x4062EF: _GLOBAL__sub_I__ZN2Ki2rdE (socket.cpp:223)
==15073==    by 0x40B2AC: __libc_csu_init (in
/home/oskar/Programowanie/build-KiSockets-Desktop-Default/tests/kisocket-test)
==15073==    by 0x59376CF: (below main) (in /usr/lib/libc-2.23.so)
==15073== Your program just tried to execute an instruction that Valgrind
==15073== did not recognise.  There are two possible reasons for this.
==15073== 1. Your program has a bug and erroneously jumped to a non-code
==15073==    location.  If you are running Memcheck and you just saw a
==15073==    warning about a bad jump, it's probably your program's fault.
==15073== 2. The instruction is legitimate but Valgrind doesn't handle it,
==15073==    i.e. it's Valgrind's fault.  If you think this is the case or
==15073==    you are not sure, please let us know and we'll try to fix it.
==15073== Either way, Valgrind will now raise a SIGILL signal which will
==15073== probably kill your program.
==15073== 
==15073== Process terminating with default action of signal 4 (SIGILL): dumping
core
==15073==  Illegal opcode at address 0x512FC65
==15073==    at 0x512FC65: std::(anonymous namespace)::__x86_rdrand()
(random.cc:69)
==15073==    by 0x512FE01: std::random_device::_M_getval() (random.cc:130)
==15073==    by 0x40659B: std::random_device::operator()() (random.h:1612)
==15073==    by 0x405ECE: __static_initialization_and_destruction_0(int, int)
(socket.cpp:26)
==15073==    by 0x4062EF: _GLOBAL__sub_I__ZN2Ki2rdE (socket.cpp:223)
==15073==    by 0x40B2AC: __libc_csu_init (in
/home/oskar/Programowanie/build-KiSockets-Desktop-Default/tests/kisocket-test)
==15073==    by 0x59376CF: (below main) (in /usr/lib/libc-2.23.so)
==15073== 
==15073== Events    : Ir
==15073== Collected : 3010559
==15073== 
==15073== I   refs:      3,010,559

Reproducible: Always

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

Reply via email to