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.
-
-
Which means that if you, say, break and your app is inside malloc() or a syscall your stack traces are useless.
-
They have unwind tables most of the time, don't they? (For non-leaf functions, anyway, I think the ABI requires that.)
- 3 more replies
New conversation -
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.