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.
Yeah, but unwind tables only cover call sites. So usually if you’re inside malloc() or whatever the stack traces are useless.
-
-
There's a recurring Nightly for Android crash (which IIRC is an Android bug, not ours) that I get and the stack trace is just beautiful. https://crash-stats.mozilla.com/report/index/a1cd9304-6734-42bd-ae4a-d03980171125#tab-details … (red = "idk wtf this frame is have fun", usually you have one or no red frames in a crash report)
- 1 more reply
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.