Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

multinode

macrumors regular
Original poster
Feb 4, 2011
150
0
A few nights ago I got an unexpected SIGABT and it looked like the problem happened inside of one of Apple's frameworks. No clues in the debugger. What usually causes a SIGABT and what is the best way to track down the problem?
 
Have you enabled breakpoints? SIGABRT generally means you tried to access a deallocated object.

What does the console tells you?

enabling NSZombies may help as well
 
Have you enabled breakpoints? SIGABRT generally means you tried to access a deallocated object.

What does the console tells you?

enabling NSZombies may help as well

Thank you.

I do use breakpoints, but the SIGABT happens immediately after returning from a method ... no chance to use breakpoints to narrow down the problem.

Open that up a bit please. How can I tell from the console that I was trying to access a deallocated object? How can enabling NSZombies answer that question? Yes, I will look at the NSZombies docs tonight.
 
SIGABRT is always because you made a connection to an IBOutlet or an IBAction and then later deleted it.

Rewire all of you IBOutlets and IBActions and see if that works...

Peace!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.