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 ] );
}
}
}
I find that catches some places I would otherwise get untrackable SIGABRTs.
On Apr 30, 2012, at 11:18 AM, Alex Zavatone wrote:
> I had the same thing Friday night or last night too.
>
> I ended up creating a new TVC, moving pieces in one at a time and in one
> case, it was the table cell name not matching.
>
> Now, I've gotten an empty TVC to work, so it's move the pieces in one at a
> time again.
>
> There are no errors when I profile the app and generally, I've seen SIGABRTs
> when I make a type and call a selector that doesn't exist or forget to wire
> up something I didn't know I need to wire.
>
> It's these types of "missing connections" I'm wondering if there are elegant
> ways to catch or trap for.
>
> In many ways, storyboarding is more difficult than programming, because you
> often can't see and don't know what needs to be hooked up or is not wired up
> properly. Some nice visual graphical hierarchy of all the required parts
> and connections that are required to work would be nice because that would
> show in one place all the connections and objects that are required and if
> they are properly hooked up.
>
> It just seems (I could be wrong) that storyboarding can be nice and graphical
> but really easy to screw up and often very hard and time consuming to figure
> out why. I've been at reassembling my app since Friday and it's not
> terribly complicated. Trial by fire I guess.
>
>
> On Apr 29, 2012, at 11:00 PM, Charlie Dickman wrote:
>
>> It sounds to me like your xib (nib) file has been "corrupted". For example,
>> it's possible that you have somehow destroyed, say, a link between an object
>> (view?) and its counterpart in your implementation or a link between an
>> object like a button or a textfield and it's IBAction.
>>
>> I suggest that you check your xib thoroughly.
>>
>> On Apr 29, 2012, at 10:50 PM, Alex Zavatone wrote:
>>
>>> I've had the joy of trying to reassemble my app which a co worker improved
>>> last week by moving it to storyboarding. What's popping up every now and
>>> then as I try to wire views together are instant SIGABRTs with no
>>> indication why this is happening.
>>>
>>> I'm currently stuck going from a TableViewController to another
>>> TableViewController and as soon as any TVC loads (even an empty one, even
>>> the same one), BLAM.
>>>
>>> The project is based off of the Tabbed Application template, has 4 tabs and
>>> all views work fine except one which has a Navigation controller that goes
>>> off to a TVC with a Nav bar at the top. When I try to nav to another TVC,
>>> as soon as it finishes displaying, (even with the same or an empty TVC), a
>>> SIGABRT happens.
>>>
>>> I've checked the table cell names, rebuilt the screen, checked Apple's
>>> samples and Ray W's book, been at this all day, to no avail.
>>>
>>> So, the big question is when a SIGABRT happens, how do each of you go about
>>> tracking it down?
>>> _______________________________________________
>>>
>>> Cocoa-dev mailing list ([email protected])
>>>
>>> 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:
>>> https://lists.apple.com/mailman/options/cocoa-dev/3tothe4th%40comcast.net
>>>
>>> This email sent to [email protected]
>>
>> Charlie Dickman
>> [email protected]
>>
>>
>>
>
> _______________________________________________
>
> Cocoa-dev mailing list ([email protected])
>
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>
> This email sent to [email protected]
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
