https://bugs.kde.org/show_bug.cgi?id=398086
Julian Seward <jsew...@acm.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsew...@acm.org
--- Comment #3 from Julian Seward <jsew...@acm.org> ---
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.
The otool command might not find the insn because it assumes that
libdispatch.dylib got mapped into memory with zero "slide" -- at the
same address that it statically contains -- which is unlikely. One
strategy is for jwz to rerun with --demangle=no --sym-offsets=yes, and
then find the insn by using the symbolname + offset pairing.
--
You are receiving this mail because:
You are watching all bug changes.
