This is an Xcode error... not your code. I am having the same problem and am fixing it now. I will let you know what to do if no one else knows before then. You can fix it yourself or wait for the patch from Apple. Hope this helps.
This is an Xcode error... not your code. I am having the same problem and am fixing it now. I will let you know what to do if no one else knows before then. You can fix it yourself or wait for the patch from Apple. Hope this helps.
Desert Sun
Do you allready have an idea? I got the same problem. How can I fix it?
Its interesting if I run it line by line the code works... if not it gives this error message...
Sorry but my developer frientd was helping me but then i have not been able to contact him... somehow I have fixed it on my computer If I can get in contact with him I will definitely post the results here.
I've fixed these several times by: cleaning all targets, shutting down xcode, softbooting my device (home+off switch), restart xcode, recompile and run. Make sure the device has a green light in the organizer too. Other than that it's witchcraft to me.
I've fixed these several times by: cleaning all targets, shutting down xcode, softbooting my device (home+off switch), restart xcode, recompile and run. Make sure the device has a green light in the organizer too. Other than that it's witchcraft to me.
What do you mean with cleaning all targets? I did everything else, but it didnt help...
Today I just had the same problem with this error. It was the first time I have experienced this. I have tried to Clean All Targets, power down my iPhone and Mac, etc... but nothing helped. The error was showing up when I was switching views (XIBs)... turned Out that I was getting this because of a [super Dealloc]?! I still did not figure out why and because of what this was happening exactly, cause when I removed the [super dealloc] and made deallocs by hand the problem did not occur... so in my case it looks like something was deallocated that shouldn't be...
Today I just had the same problem with this error. It was the first time I have experienced this. I have tried to Clean All Targets, power down my iPhone and Mac, etc... but nothing helped. The error was showing up when I was switching views (XIBs)... turned Out that I was getting this because of a [super Dealloc]?! I still did not figure out why and because of what this was happening exactly, cause when I removed the [super dealloc] and made deallocs by hand the problem did not occur... so in my case it looks like something was deallocated that shouldn't be...
Could you please tell me from where i need to delete the Dealloc? i have same error when i try to swith XIBs. From which .m should i delete it? from the one that is the main or the second one?
HElp
Mine was a simple issue of case sensitivity... i had renamed the classes because I wanted and uppercase letter where I had a lower case letter. I did not however change the xib file to match... this affected my code in the info section in interface designer the class is listed that represents the xib file... it was still lowercase... fixed that and change the case of the xib file name just to keep it uniform... that fixed the error for me.
So it could be as simple as incorrect case... it worked in simulator just fine... but not on a device.
For SIGABRT errors, run in debug until the program crashes. Then, there should be a little black button with the text "GDB" in yellow over it above your code editor in your mini-debugging bar. Click it, and it will bring up your debugger console. This should show the sig-abort report, possibly an alert stating that it was caused by an unhandled thrown exception, the stack trace of all nested function calls, and above that, one or more messages dealing with what specifically went wrong.
I don't know what is wrong with the actual startup error, but it could be very likely you changed the name of some class in your code that was referenced by your xib files, and didn't change the references in Interface Builder.
Another heads up, that's exactly the problem I had. I had renamed both the default app delegate and default view classes given in the startup OpenGL project, and never updated the references in Interface Builder.
I kept getting a GDP Exeption that my glView property/outlet (because the default view type was changed, and so didn't exist anymore) could not be key-value coded, or something like that. It was dynamically typed so it never threw a compiler error. Also, I had renamed glView to gameView, and it didn't update in IB. God, I hate Apple.
Anyway, if that is your case, you have to go to interface builder and change the "Class" in "Identity" of each invalid object. Then, make sure all connections are valid and correct.
another possibility is that backgrounder (a cydia app to allow multitasking) cause it. So open backgrounder and add a "ovverride" to your app, so SIGABTR will be not appear the next time.
99% is not your case, but i want to say it, because maybe someone in fucture will have this problem (as me )
These sorts of errors are very common. I think you guys are right, it is the due to the changed names, and classes which mismanage the references and creates problems with interface builder.
I'd just completed the 'hello world' tutorial and kept getting SIGABRT errors. I checked the spelling of all variables and terms and it wouldn't work.
Then I changed the font from "Futura-MediumItalic" (used in the tutorial) to "Helvetica" and it finally worked. Somehow I must have deactivated the font...I use FontExplorerX Pro, maybe this was the problem...
I'd just completed the 'hello world' tutorial and kept getting SIGABRT errors. I checked the spelling of all variables and terms and it wouldn't work.
Then I changed the font from "Futura-MediumItalic" (used in the tutorial) to "Helvetica" and it finally worked. Somehow I must have deactivated the font...I use FontExplorerX Pro, maybe this was the problem...
I only ever get this error when the app is calling on something that is missing from resources.
e.g I have an (IBAction) which plays a sound but the sound is no longer part of the app.
Check all of your called resources in your code and make sure they're still in your xcode project. Even images used in Interface builder can produce a SIGARBT.
It's an annoying error because 9/10 times the debugger doesn't tell you what's wrong.
I know there is probably a better way to do this with breakpoints, but I always like to use NSLog statements to narrow down the point that is causing the failure. A lot of times it is something simple like releasing something too many times, or trying to access something that has already been released.
__________________
Check out our newest app, SpectaRuler™
Recently featured on Apple's New and Noteworthy and What's Hot Utilities lists!
Well....
This also happened to me. Whenever I ran the app, the simulator crashed and the debugger said: Program received SIGABRT
In the bold, I noticed an object that I previously deleted. So I went all into my files, but could not find it. It turned out that the object in the IB was still linked with my old methods and things that I already deleted.
Hope this works for u too!
SIGABRT?!?!?!?!?
If I can get in contact with him I will definitely post the results here.
)
Linear Mode
