https://bugs.kde.org/show_bug.cgi?id=492886
--- Comment #7 from localtoast <ipsum.te.fu...@gmail.com> --- (In reply to Sam James from comment #6) > Ignore everything >= the unrecognised instructions bit as it means Valgrind > can't correctly model everything from then on. But the part before is > curious. I found bug 488591 at least but it's not the same. > > I found https://github.com/i3/i3lock/issues/73 which links to > https://bugreports.qt.io/browse/QTBUG-56518. It looks like a mess but not > related. So, Valgrind is a dead-end for this bug unfortunately. > > ASAN and UBSAN time if you'd be so kind? :) Ok so I have to admit that I don't know what you're asking for at this point. A quick Google to appear on the ball tells me these are gdb report modes, and can be enabled by rebuilding something with -fsanitize makeopts, but I'm unclear what I need to rebuild - gdb, gcc, plasmashell, qtbase, something else? -- You are receiving this mail because: You are watching all bug changes.
