Skip to content
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

Open
ffrlx opened this issue May 6, 2020 · 6 comments
Open

Support for Extended ASCII Codes #46

ffrlx opened this issue May 6, 2020 · 6 comments

Comments

@ffrlx
Copy link

ffrlx commented May 6, 2020

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.

@ThunderCls
Copy link
Owner

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.

@ffrlx
Copy link
Author

ffrlx commented May 6, 2020

Debugger and xAnalyzer

Sorry, english it's not my native language.
About the plugin. Look image.

@ffrlx
Copy link
Author

ffrlx commented May 6, 2020

When I do a new compilation, in debbuger the hexdump is correct, but in disassembler it is not.

@ThunderCls
Copy link
Owner

ThunderCls commented May 6, 2020

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

@ffrlx
Copy link
Author

ffrlx commented May 6, 2020

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.

@ThunderCls
Copy link
Owner

Yeah so far it doesn't support those, but it will in the next major version.
Thanks for reporting!

@ThunderCls ThunderCls added this to the v3.0 milestone May 6, 2020
@ThunderCls ThunderCls changed the title XAnalyzer - The Code is changed, but does not change in the debugger. Support for Extended ASCII Codes May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants