Ilmari Lauhakangas kirjoitti 21.8.2018 klo 15.20:
Can anyone use valgrind anymore? I keep getting this when trying to get
a callgrind trace with a master build:
Solved by updating from valgrind 3.12 to 3.13.0+290+2b0aa0a5-1 (from
Arch Linux repo).
Thanks to jmux for inspiration.
Ilmari
Can anyone use valgrind anymore? I keep getting this when trying to get
a callgrind trace with a master build:
vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0x1E 0xFA 0x55 0x48
0x89 0xE5
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
