SIGABT ... how to debug this kind of problem

Discussion in 'Mac Programming' started by multinode, Sep 3, 2013.

  1. multinode macrumors regular

    Feb 4, 2011
    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?
  2. Sonnestah macrumors regular

    Mar 2, 2013
    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
  3. multinode thread starter macrumors regular

    Feb 4, 2011
    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.
  4. blackenedheart macrumors newbie

    Sep 3, 2013
    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...


Share This Page