Hey ^^
Does anyone know why SIGABRT could be thrown?
I can't figure out why it's thrown :/
A fast, easy to use, free, and community supported 2D game engine
Hey ^^
Does anyone know why SIGABRT could be thrown?
I can't figure out why it's thrown :/
SIGABRT is the signal sent when the program is attempting to abort itself. Generally this is because something really bad has happened.
I've gotten it a few times and generally fixed it by making sure I'm not releasing too early... Those kind of things.
Could be lots of things...
For example, calling a method on an object which doesn't have it.
Check the console, it always tells you where the sigarbt occurred.
I could be remembering wrong, but isn't SIGABRT what you get when there's an uncaught exception?
Step 1: Check console, look at the last few messages before the stack list.
Step 2: Turn breakpoints on, check debugger.
The problem was, console said only "Abort Trap".
But actually I got it, I made it myself xD
It was an assertion failure :(
@pabloruiz55: How exactly do I find where it happens through the console?
At least in my experience, these happen when I am doing things with either C or C++, Not objective C (but they still could). Are you using chipmunk or any other physics engine?
I am not. I am just wondering how am I supposed to find where something like SIGABRT happened through the console message.
SIGABRT generally comes with a pretty clear error message in the debugger. typing "bt" will also give you the backtrace which will tell you where exactly it crashed.
Ah, thanks, found the problem.
You must log in to post.