Summary: | vex amd64->IR: unhandled instruction bytes: 0xC5 0xD4 0xC2 0xED 0xF 0xC5 0xFC 0x29 0xAC 0x24 | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | peoro <paolo> |
Component: | vex | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | mark |
Priority: | NOR | ||
Version First Reported In: | 3.14.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
peoro
2019-04-19 04:21:44 UTC
(In reply to peoro from comment #0) > I'm playing around with QtWebKit and WebGL. The program runs smoothly > without valgrind, while valgrind makes it fail: > > vex amd64->IR: unhandled instruction bytes: 0xC5 0xD4 0xC2 0xED 0xF 0xC5 > 0xFC 0x29 0xAC 0x24 > vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 > vex amd64->IR: VEX=1 VEX.L=1 VEX.nVVVV=0x5 ESC=0F > vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 > ==7397== valgrind: Unrecognised instruction at address 0x540b16fe. c5d4c2ed0f vcmptrueps ymm5,ymm5,ymm5 So I suspect this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=399287 Which was fixed for the just release valgrind 3.15.0. Could you re-try with that version? Oh, I'm sorry, I wasn't able to find the other bug report. I just built valgrind 3.15.0 and indeed it doesn't fail. Thanks! *** This bug has been marked as a duplicate of bug 399287 *** |