[valgrind] [Bug 429424] vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0 (lock or)

2022-01-04 Thread Oliver Kellogg
https://bugs.kde.org/show_bug.cgi?id=429424 Oliver Kellogg changed: What|Removed |Added Resolution|LATER |FIXED Status|NEEDSINFO

[valgrind] [Bug 429424] vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0 (lock or)

2022-01-03 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=429424 --- Comment #4 from Mark Wielaard --- (In reply to Oliver Kellogg from comment #3) > I tried again with valgrind-3.17.0 on Tumbleweed 20211012 and the messages > are different: > > > valgrind ./umbrello/umbrello5 > == Memcheck, a memory error detector

[valgrind] [Bug 429424] vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0 (lock or)

2022-01-03 Thread Oliver Kellogg
https://bugs.kde.org/show_bug.cgi?id=429424 Oliver Kellogg changed: What|Removed |Added Resolution|--- |LATER Status|REPORTED

[valgrind] [Bug 429424] vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0 (lock or)

2021-02-28 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=429424 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org Summary|vex amd64->IR

[valgrind] [Bug 429424] vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0

2020-11-21 Thread Oliver Kellogg
https://bugs.kde.org/show_bug.cgi?id=429424 --- Comment #1 from Oliver Kellogg --- FWIW, here is the GDB backtrace from the vgcore file: Program terminated with signal SIGILL, Illegal instruction. #0 __GI_raise (sig=4) at ../sysdeps/unix/sysv/linux/raise.c:45 #1 0x08a34dcf in KCrash::d

[valgrind] [Bug 429424] vex amd64->IR: unhandled instruction bytes: 0xF0 0xC 0x0

2020-11-21 Thread Oliver Kellogg
https://bugs.kde.org/show_bug.cgi?id=429424 Oliver Kellogg changed: What|Removed |Added Summary|vex amd64->IR: unhandled|vex amd64->IR: unhandled |in