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

Cannot use hotkeys, such as F7/F8, while analyzing #24

Open
justanotheranonymoususer opened this issue Aug 31, 2017 · 8 comments
Open

Comments

@justanotheranonymoususer
Copy link
Contributor

No description provided.

@ThunderCls
Copy link
Owner

you're not supposed to be stepping while the plugin is analyzing, like IDA, Olly, etc...you need to wait till the process is done

@justanotheranonymoususer
Copy link
Contributor Author

I don't see why that's so in x64dbg. I mean, what could go wrong if you allow stepping?

Also, even if you choose to disable the hotkeys, at least don't make them step all at once when analysis finishes. Currently, pressing F7 (for example) multiple times during analysis will result in sudden stepping after analysis is done.

@justanotheranonymoususer
Copy link
Contributor Author

Also, some navigation buttons, such as Home/End, don't work, even though others, such as page up and page down, do work.

@ThunderCls
Copy link
Owner

Well, that's how x64dbg works, so far this is issue is not related to the plugin itself so you could post this on the x64dbg github page or perhaps ask directly on the telegram channel.

@justanotheranonymoususer
Copy link
Contributor Author

What do you mean? It only happens while analyzing

@ThunderCls
Copy link
Owner

What I mean is that thats the "lock system" that x64dbg currently has. If you try opening a big executable 10-20MB in the debugger without the xAnalyzer plugin and execute a couple x64dbg own analysis algorithms (commands "cfanal", "analx", etc) you'll realize that stepping (F7/F8 etc) is gonna be locked till the analysis is completed. That's how x64dbg works, that's what I mean

@justanotheranonymoususer
Copy link
Contributor Author

OK. Still, it would be nice if there was a workaround...

@ThunderCls
Copy link
Owner

I guess I could go with DbgCmdExecDirect on a separate thread. I'm reopening this for a future version/revision.
Thanks

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