Game Development Community

SIGABRT blues

by rennie moffat · in iTorque 2D · 11/11/2010 (9:44 pm) · 6 replies

HI there,
I am doing some updates to my app, but am getting a SIGABRT Error. Some google searches have suggested, that a) something major is wrong, b) that something is wrong with XCode and a few resets, cleans etc will alleviate it. Well b) is true, except it continues to happen.


The trouble first arose when I did not plug in a value for a schedule that was to loop. It froze the game, no problem. I am not sure if this is the root, but it was my suspicion, problem is, as I say is that it continues.


The error message I get in the console is this:
Couldn't register TempleRacerDomain with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.Program received signal: “SIGABRT”.



If anyone has any tips on how to trouble shoot this I would really appreciate it.

Thanks.

About the author

My thanks to Garage Games and the Garage Games Community combined with owned determination I got one game up, Temple Racer and I am looking to build more interesting, fun games for the mass market of the iOS app store.


#1
11/11/2010 (10:17 pm)
ps.

i am not getting any errors in script from the iTGB console.
#2
11/11/2010 (10:57 pm)
just for the record it has started running consistently, funny how when I post here, things tend to fix themselves, however, for future reference, if anyone has trouble shooting tips etc, I would like to hear them.


thanks
#3
11/12/2010 (12:22 am)
It has returned.
If anyone has a clear definition, can provide a better understanding for me, it would be appreciated.

Thanks.
#4
11/12/2010 (9:11 pm)
I may have permanently fixed it, or found a fix.. just turn your iDevice off, thurougly, like reboot it.



I know this is more of an XCode problem, but anticipating its return, again, if anyone has any other experiences with this, and potential solutions, please pass along.


Thank You.
#5
11/13/2010 (3:05 am)
Thanks for the fix Rennie - I ran into this error recently myself and worked around it by switching to another device. Good to know a reboot is all that's necessary.
#6
11/13/2010 (3:15 am)
Yah it seems that rebooting the IDevice itself is the fix. I was forever rebooting the computer. My bad.



And for the record, my SIGABRT came from a missing value cause a loop to not run. Crashed everything and XCode "couldn't forget about it", until the iDevice was rebooted.