-
Notifications
You must be signed in to change notification settings - Fork 112
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
Support for Extended ASCII Codes #46
Comments
I'm sorry but I don't quite understand your statement. Are you referring to the debugger or the plugin? Can you elaborate? You can use screenshots if you want. |
When I do a new compilation, in debbuger the hexdump is correct, but in disassembler it is not. |
New changes done to the binary are not automatically reflected by the plugin in the function comments, you need to manually launch a new analysis so the data can be updated to the newest. In this case, for instance, since you're only modifying one specific function data, you could just select every argument and perform a "selection" analysis with the plugin, values should update just fine |
Okay, this worked. Any chance to implement for words with special characters (for instance: á, é, í, ó, etc.)? Words with these characters do not appear in the debugger comments. Thank you. |
Yeah so far it doesn't support those, but it will in the next major version. |
Hi!
XAnalyzer is not updating the function parameters, even with automatic analysis on. If I modify a string, the debugger x32dbg, apparently, takes the previous code that is in the DB folder. All cleaning options are on. Is there a solution? Is it possible for XAnalyzer to recognize all ASCII table characters? For instance: recognizing strings like 0x82, 0xA0, etc. I'm using the latest version of x64dbg and xAnalyzer.
Thanks.
The text was updated successfully, but these errors were encountered: