New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes "ida.exe" #7
Comments
I actually got some small .idb to run without crashing. But then other larger ones crash IDA every time. I see in the Ghidra source: Are you sure that error handler catches low level exceptions like access violations? Easy enough to test. At the top of your try/catch statement do a |
No you are right, access violation, for example, are not handle. But most of the time it's come from IDA or Ghidra, and I prefer to end the process if an access violation happened. LowLevelError is the name of Ghidra's exceptions. |
I doubt your typical IDA user prefers this behavior. Should an add-on/plugin exit IDA when it fails? What if the user didn't do a save recently? With the low level handler you can catch the most common crash (access violation) without having to exit. |
I finnaly manage to reproduce a crash due to an infinite recursive loop in type solve algorithm. I will try to produce a release before end of the week! |
This is due to cyclic reference in type tree... |
Tried running Yagi for IDA 7.6. 64 bit runs fine, but the 32bit target "ida.exe" will crash almost instantly, and without any sort of dialog/warning box.
Consider wrapping your IDA "run" in an a C or C++ exception handler.
It's what I do, great for development. With a
msg()
in the handler it will tell me my plugin crashed instead of crashing IDA (most of the time anyhow, could cause IDA to crash outside of our plugin space et al).The text was updated successfully, but these errors were encountered: