-
Notifications
You must be signed in to change notification settings - Fork 48
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
Improve known cheat code errors #497
Comments
Hi @arcz, Thanks for this! I have done some work on this, but for the life of me I can't find a way to test it 😆 Please see PR #503 There, the file So I'm stuck at testing my new fix. Do you know how could I write that inline assembly such that the interpreter will die with a Thanks, Mate |
Blocked currently on a good test case and a follow-up review. Perhaps in September when fewer people are on vacation, this will be merged :) |
We return non-helpful errors when there is a problem with a known cheat code. For instance, here we know we are inside
ffi
but we returnBadCheatCode
withsig
which doesn't add much debugging value.Ideally, in the error, we should have the method + args like
ffi(string[])
and a failure reason.The text was updated successfully, but these errors were encountered: