Re: Tracking down SIGABRTs
Re: Tracking down SIGABRTs
- Subject: Re: Tracking down SIGABRTs
- From: Alex Zavatone <email@hidden>
- Date: Sun, 29 Apr 2012 23:45:03 -0400
Ahh. Well, I changed it back from HIPAppDelegate to AppDelegate and when the SIGABRT happens, the catch isn't catching it. I set a breakpoint on NSLog and it's never triggered.
Am I assuming too much here?
On Apr 29, 2012, at 11:35 PM, Roland King wrote:
> That's autogenerated code, came from the project template.
>
>
> On Apr 30, 2012, at 11:33 AM, Alex Zavatone wrote:
>
>>
>> On Apr 29, 2012, at 11:26 PM, Roland King wrote:
>>
>>> At least during development I do this to main.m
>>>
>>> int main(int argc, char *argv[])
>>> {
>>> @autoreleasepool {
>>> @try
>>> {
>>> return UIApplicationMain(argc, argv, nil, NSStringFromClass([HIPAppDelegate class]));
>>> }
>>> @catch (NSException *exception)
>>> {
>>> NSLog( @"Exception in main %@\n%@", [ exception description ], [ exception callStackSymbols ] );
>>> }
>>> }
>>> }
>>
>> Awesome. What's the renaming of AppDelegate? HIPAppDelegate
>>
>
_______________________________________________
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