We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am disassembling with try catch something that may be valid opcodes or not (just whole memory of a program).
For example I am hitting a debug assert at Udis86/Decode.cs line 429.
Debug.Assert(u.error == 0, "invalid operand size");
Currently I am working around it using http://stackoverflow.com/questions/2854024/how-to-prevent-debug-assert-to-show-a-modal-dialog, but I think it would be better to have a better failure mode when invalid operations are encountered.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am disassembling with try catch something that may be valid opcodes or not (just whole memory of a program).
For example I am hitting a debug assert at Udis86/Decode.cs line 429.
Debug.Assert(u.error == 0, "invalid operand size");
Currently I am working around it using
http://stackoverflow.com/questions/2854024/how-to-prevent-debug-assert-to-show-a-modal-dialog, but I think it would be better to have a better failure mode when invalid operations are encountered.
The text was updated successfully, but these errors were encountered: