IIRC it wasn't actually a miscompile, it was a bug in their libs, coupled with some weird codegen around class inheritance and exceptions. The same binary would work on Lollipop but fail on M. For a specific libc (glibc I think?). I don't remember anymore; it was really weird.
-
-
Note that on ARM EABI, because of no frame pointers, you cannot get a stack trace past ANY system library function without DWARF debug info.
-
Which means that if you, say, break and your app is inside malloc() or a syscall your stack traces are useless.
- 4 more replies
New conversation -
-
-
yes, that was the case.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.