Ah, it's 32-bit iOS. (I assumed i386 or x86_64 from the unaligned instruction
addresses, but forgot that 32-bit ARM can have those too.) The small-looking
addresses are okay, then.
That +437720 is still bogus. Ordinarily a symbol with a large offset means that
the code was actually in some othe
These crashes are uploaded from device, namely an iPad 4 (running the app in
compatibility mode) uploaded through Crashlytics and then downloaded from
there. I haven’t been able to reproduce the crash and so I haven’t seen a raw
dump. Here’s the full crash stack, redacted, from an iPad 4 running
> On Feb 13, 2017, at 12:18 PM, Jon Shier via swift-users
> wrote:
>
> Swift Users:
> I’m currently seeing a crash in my iOS app that has no apparent cause,
> but a bit of Swift runtime machinery in the stack has me confused.
>
> #0. Crashed: com.apple.main-thread
> 0 App
Swift Users:
I’m currently seeing a crash in my iOS app that has no apparent cause,
but a bit of Swift runtime machinery in the stack has me confused.
#0. Crashed: com.apple.main-thread
0 App0x665ac
Controller.handleOtherNotification(Notification) -> () (Controll
