How can I fix this SIGABRT error with my app?

Question

I am currently developing an app in Xcode 4 for the IPhone and I have com across this error, "Thread 1: Program Received Signal: SIGABRT", This error is in my main.m code.

//
//  main.m
//  MyCard
//
//  Created by Nazar Gren on 2/2/12.
//  Copyright (c) 2012 Nazar Gren. All rights reserved.
//

#import <UIKit/UIKit.h>

#import "mycardAppDelegate.h"

int main(int argc, char *argv[])
{
     @autoreleasepool {
        return UIApplicationMain(argc, argv, nil, NSStringFromClass([mycardAppDelegate         class]));
     }
 }

My error appears on the line under the @autorelease pool line. In the debugger, I get this message, "This generally means that another instance of this process was already running or is hung in the debugger." And this error only occurs when I attempt to debug my app. My app doesn't even run. Can anyone help? It would be greatly appreciated.

None of these helped. Can I send my project to any of you via EMail to fix? I am fairly new to Xcode. — user1186514, Feb 05 '12 at 19:59

score 8 · Answer 1 · answered Feb 03 '12 at 02:09

8

If this is happening on the simulator, restart your computer. If this is happening on a real device, restart the device, and if the problem persists, restart the computer as well. This problem has occurred for me multiple times, because of a zombified process left on the device/simulator when a test is unexpectedly aborted. A simple reboot will fix it.

answered Feb 03 '12 at 02:09

eric.mitchell

8,817
12
54
92

None of these helped. Can I send my project to any of you via EMail to fix? I am fairly new to Xcode. – user1186514 Feb 05 '12 at 20:00
1

This error has nothing to do with your project. You have rebooted all of the devices involved and not resolved the problem? – eric.mitchell Feb 05 '12 at 20:25
Could you show the solution to the problem that you used so future users with the same problem can be helped? – eric.mitchell Feb 08 '12 at 22:57
Ya, for the error that I got in the debugger, I restarted the mac and it worked. – user1186514 Feb 09 '12 at 21:30
If my answer solved your problem, you should mark it as the solution for future users. – eric.mitchell Feb 09 '12 at 23:32
I restarted my computer its still not working – Vineesh TP Jun 06 '12 at 05:38
This didn't work for me but worth a try for others I suppose. – AntiPawn79 Mar 18 '23 at 14:37

score 2 · Answer 2 · edited May 23 '17 at 12:25

All your code gets run through the main.m. So what you really want to see is a stack trace and there's is a good example here, but I see you're using the autoreleasepool so you'll need something like

//
//  main.m
//  MyCard
//
//  Created by Nazar Gren on 2/2/12.
//  Copyright (c) 2012 Nazar Gren. All rights reserved.
//

#import <UIKit/UIKit.h>

#import "mycardAppDelegate.h"

int main(int argc, char *argv[])
{
     @autoreleasepool {
        @try {
            return UIApplicationMain(argc, argv, nil, NSStringFromClass([mycardAppDelegate class]));
        } @catch (NSException *e) {
            NSLog(@"CRASH: %@", e);
            NSLog(@"Stack Trace: %@", [e callStackSymbols]);
        }
     }
 }

None of these helped. Can I send my project to any of you via EMail to fix? I am fairly new to Xcode. — user1186514, Feb 05 '12 at 20:00

score 1 · Answer 3 · answered Feb 03 '12 at 01:49

1

This is not in Main code. Can be anywhere. Please try zombie tool in instruments. You are probably trying to access an object which has been already released. NSZombie will tell you which is the object and you can investigate from there.

answered Feb 03 '12 at 01:49

mbh

3,302
2
22
24

None of these helped. Can I send my project to any of you via EMail to fix? I am fairly new to Xcode. – user1186514 Feb 05 '12 at 20:00
@user1186514, how did you fixed your issue (Signal Sigabart), i am also facing same issue in my app, i tried somany ways, but i dint figuredout, could you please suggest me how you had handle that issue? Thanks in advance! – Anilkumar iOS - ReactNative Jan 12 '15 at 12:57

score 1 · Answer 4 · answered Feb 06 '12 at 18:55

1

Did you remove a reference to something attached in your main storyboard?

If so, checkout the referencing outlets of that object to see if it's still trying to point to something, try removing that reference and running your simulator again...

answered Feb 06 '12 at 18:55

Thierry Blais

2,848
22
41

How can I fix this SIGABRT error with my app?

4 Answers4

Linked