Re: Tracking down a strange SIGABRT
Re: Tracking down a strange SIGABRT
- Subject: Re: Tracking down a strange SIGABRT
- From: Ken Thomases <email@hidden>
- Date: Wed, 11 Apr 2012 22:18:16 -0500
On Apr 11, 2012, at 8:27 PM, Alex Zavatone wrote:
> I've got a stange situation that just started happening on one of my devices and only on this device.
>
> Not using ARC (yet), no memory leaks.
>
> Thread one gets a SIGABRT when I load a view, but only on this one device (IPod Touch Gen3) running iOS 5.0.1. It was working fine all day, then it just started happening. I've narrowed it down to the display of a view and will continue to debug, but I am curious about how this happens only on one device.
>
> I've tested this on two other iPods and iPhones and the 5.0 simulator running 5.0.1 and they display the view without a problem.
>
> Crash logs are not being written out.
>
> Annnd I just restarted the device and all is fine. Something must be leaking somewhere. Hmmmmm.
Could be an uninitialized variable. You may have been getting a garbage value that caused a crash on the one device because that's what was in memory, but on other devices (and the one device after a restart) getting a different value that doesn't cause a crash. Run the static analyzer against your code.
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden