Re: [Valgrind-users] Possible bug in valgrind?

2014-09-09 Thread Philippe Waroquiers
On Tue, 2014-09-09 at 22:39 +0200, Tobias Widlund wrote: > > vex amd64->IR: unhandled instruction bytes: 0xF 0x1 0xD5 0x31 0xC0 > 0xC3 0x48 0x8D > 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.

Re: [Valgrind-users] Possible bug in valgrind?

2014-09-09 Thread Julian Seward
This is HTM lock elision stuff; 3.9.0 doesn't support it but 3.10.0.BETA2 might well do. > I have tried googling on this error but I am not finding much related to > it. Any ideas on how to fix it? Try with http://www.valgrind.org/downloads/valgrind-3.10.0.BETA2.tar.bz2 instead. J ---

[Valgrind-users] Possible bug in valgrind?

2014-09-09 Thread Tobias Widlund
Hello! I am having issues using valgrind on my project. I am getting an "Illegal opcode" error. This is the full invocation and the log: 132 tobbe@archosaurus ~/projects/blocks (git)-[master] % valgrind ./bin/blocks :( ==21008== Memcheck, a memory error detector ==21008=