https://bugs.kde.org/show_bug.cgi?id=387940
Thomas A. F. Thorne <taftho...@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |taftho...@googlemail.com
--- Comment #1 from Thomas A. F. Thorne <taftho...@googlemail.com> ---
I believe that I have replicated at least part of the issue covered by this bug
report. That could move the status to confirmed as happening to more than 1
user on one machine.
The background is stored on
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1765001
In short, I was running valgrind --leak-check=yes against a binary that I
generated with g++ (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 and the
resulting output from Valgrind included:
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
==9424== valgrind: Unrecognised instruction at address 0x4ef1b15.
==9424== at 0x4EF1B15: ??? (in
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==9424== by 0x4EF1CB1: std::random_device::_M_getval() (in
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==9424== by 0x43CFBC: std::random_device::operator()() (random.h:1612)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
==9424== valgrind: Unrecognised instruction at address 0x4ef1b15.
==9424== at 0x4EF1B15: ??? (in
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==9424== by 0x4EF1CB1: std::random_device::_M_getval() (in
/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21)
==9424== by 0x43CFBC: std::random_device::operator()() (random.h:1612)
The Ubuntu bug was generated after I got a crash report prompt. It seems that
running:
valgrind --leak-check=yes -v
without having the valgrind-dbg package installed casued something that Ubuntu
did not like to happen. Once I installed the debug package to see if it would
help the Ubuntu debug tracing, the crash stopped happening.
--
You are receiving this mail because:
You are watching all bug changes.
