Menu
I have a strange problem, i am getting a Sigabrt in main loop, but no error message is displayed, i've looked quite a lot on this in the internet but didn't manage to find anything useful. So my question would be, how to track what is causing sigabrt with no error message?
Thanks in advance.
741
Use the exception breakpoint to gather extra information for the SIGABRT crash, and then disable it once you've solved the bug (until it's needed again).
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.
A SIGABRT (signal abort) error means that the app was deliberately crashed due to some really bad problem, like a runtime error during the start-up sequence or a bad or unreadable user interface file.
SIGABRT errors are caused by your program aborting due to a fatal error. In C++, this is normally due to an assert statement in C++ not returning true, but some STL elements can generate this if they try to store too much memory.
When your program crashes, you can go to the debugger console and type bt (backtrace) which will give you an idea of what code was being executed at the time of the crash. The top level items may not be your code, but if you keep moving down you should see something of yours in there eventually.
If there aren't any calls from your code then these SIGABRT errors are often related to your xib files, there will be something missing or renamed or otherwise changed in a xib file that hasn't been reflected in your code.
85
For way too long, I thought the console was giving me no information with XCode 8 but then I realized I just had hidden the console and needed to show it again.
For anyone else stuck in a weird brain warp like I was:
Press that button and see what XCode is telling you is broken, fix it
Enjoy life again!
40
Have you looked in the logs?
Have you tried running in the debugger? It should stop and give you a stack trace when it. Also try setting a break point on all exceptions.
43
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
