libc++abi.dylib: terminating with uncaught???

Monkey Targets Forums/iOS/libc++abi.dylib: terminating with uncaught???

MikeHart(Posted 2014) [#1]
With XCode 5.0.2 on OSX 10.8.6 and a pretty bare ass project, I get this error now:

libc++abi.dylib: terminating with uncaught exception of type char const*

Did you ran into this before? Any idea what could have caused this?


MikeHart(Posted 2014) [#2]
Ok, it seems that the use of Error crashes the app like this.

Error("Error in method ftEngine.New: Could not load image ftLoadingBar.png!")

But the message I wanted to throw out there was not to be seen. :-/


rIKmAN(Posted 2015) [#3]
Sorry to bump such an old thread, but this is a still a thing.

Just had the same error: libc++abi.dylib: terminating with uncaught exception of type char const* and Googling it actually brought me to this thread, I think it was the 3rd result listed.

I thought it was a bug with opening the keyboard but it was the line before it which was using Error.

Thanks for replying to your own post with the solution Mike, many don't when nobody answers, and it has saved me some frustration a year later. :)


MikeHart(Posted 2015) [#4]
Thanks for replying to your own post with the solution Mike, many don't when nobody answers, and it has saved me some frustration a year later. :)


You're welcome. A solution.... I didn't had one besides not using Error in Release mode.


rIKmAN(Posted 2015) [#5]
Well...solution, workaround, cludge....call it what you want but it saved me some time and some hair so thank you! :)