Answer the question
In order to leave comments, you need to log in
What can be done with SIGSEGV in a third-party library or how to catch an error in my own?
Greetings!
I'm working with a third-party library and after some time (no more than 10 minutes) it crashes into SIGSEGV
The debugger points to something in the library itself, but its code is closed.
Maybe I'm giving her something wrong.
Tell me, is there a way to catch SIGSEGV in c++ mingw 4.9.2 qt5 without crashing?
Or how can I understand what happens in the library if the debugger only refers to the asm code (I can’t understand what it doesn’t like because all the parameters and calls with sigsegv are the same as before and the debugger refers to different places O_o)?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question