https://bugs.kde.org/show_bug.cgi?id=398086
--- Comment #4 from Rhys Kidd <rhysk...@gmail.com> --- (In reply to Julian Seward from comment #3) > It didn't actually print the undecodeable bytes, as it normally does in > such cases. So I'd guess the "failing" insn is ud2 for which I think we > indeed don't print the failing bytes. If I had to guess I'd say it is > libdispatch.dylib's way of throwing a fatal assertion failure following > the syscall failures, which it presumably can't recover from. Makes sense. I recall seeing something similar before in another occasion where valgrind didn't provide support for a mach syscall, and a 'ud2' error was hit shortly thereafter. I'll leave this bug open for now, but suspect it will be addressed by the eventual fix for bz#383199 which provides unix:463 (openat) support. -- You are receiving this mail because: You are watching all bug changes.
