Post

Replies

Boosts

Views

Activity

Reply to Callstack of a std::exception does not include the location of the throw
Yes, I would like to find out why my app crashed, Its likely due to a c++ exception that's incorrectly handled by my code. But there is no way of fixing it until I know where it has been thrown. All suggestions are welcome as this has become a serious issue for us. We are using the Qt framework and except from complaining users the only thing we get is the crashes in test flight (with a call stack that is not providing insight). Is there any way of disabling the catch all in the run loop? Is there any way of getting the exception .what() information in the test flight log?
Apr ’24