I just ran into this problem on xenial, but I wanted to inquire whether
there is any plan to backport the patch before I try to compile it
myself. Can we expect the fix in xenial any time soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Hi Matthias,
I was affected by this bug and can confirm, that applying the linked patch
fixes the issue on ubuntu 16.04 (Xenial Xerus) on a i7-6600U.
It would be nice if the patched could be backported to Xenial as it's
tedious to recompile valgrind on every update to get it functional
again.
-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: valgrind (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501545
Tit
please could somebody confirm that backporting the patch for this issue
solved the problem?
** Also affects: valgrind (Ubuntu Zesty)
Importance: Medium
Status: Confirmed
** Also affects: valgrind (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: valgrind (U
Installing valgrind 1:3.12.0~svn20160714-1ubuntu2 from yakkety onto my
xenial machine seems to resolve the issue, too. But probably including
the patch from https://bugs.kde.org/show_bug.cgi?id=353370#c9 will be
easier than doing an update in xenial, right?
--
You received this bug notification b
We are seeing this bug with valgrind 1:3.11.0-1ubuntu4.1 on 16.04 in our
Ceph testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501545
Title:
Valgrind fails on rdrand when the cpu supports it
I can confirm the problem on 16.04 and I can also confirm that the patch
posted in kde-bugs #353370 report seems to fix the issue (valgrind
compiled from source with and without the patch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I also get the same error on Ubuntu Wily + Valgrind 3.11 + g++ 5.2
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.n=0x0 ESC=0F
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
I get the exact same error and bytes.
unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x6 0xF 0x42 0xC1
It happens when using std::random_device with GCC 5.2 on willy.
It's weird GCC stopped using /dev/urandom, a very good randomness source
that makes use of RDRAND
--
You received this bug noti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: valgrind (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501545
Title:
V
** Tags added: wily
** Changed in: valgrind (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501545
Title:
Valgrind fails on rdrand when the cpu supports i
This upstream bug looks related (affecting rdrand) but the instruction
bytes are different:
https://bugs.kde.org/show_bug.cgi?id=353370
** Bug watch added: KDE Bug Tracking System #353370
https://bugs.kde.org/show_bug.cgi?id=353370
** Also affects: valgrind via
https://bugs.kde.org/show_bu
** Description changed:
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.n=0x0 ESC=0F
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
opcode "rdrand %eax"
+ Need val
13 matches
Mail list logo
