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

Inconsistent register dumps of 32-bit WoW64 targets between bdump.js and snapshot #8

Closed
ducphanduyagentp opened this issue Jul 25, 2024 · 3 comments · Fixed by 0vercl0k/dbgeng-rs#3

Comments

@ducphanduyagentp
Copy link

While trying to get WTF to work with a test 32-bit program, I encoutered issues when tracing the execution for debugging purposes. It keeps generating page fault, resulting in CR3 and crashes. I followed every step recommended on WTF's README to no avail, even after reading a few blogposts from people that tried and had issues with 32-bit programs.

It turned out that the issues was due to some differences in regs.json in bdump.js and snapshot. I followed exactly what described in those posts and the only difference was that snapshot wasn't available at the time.

In the value of cs, ds, es, gs, ss, the limit was 0xffffffff in bdump and 0xfffff in snapshot. Changing these values in snapshot's regs.json makes the trace run as expected for me.

This only happens to 32-bit targets. I compiled the same program in 64-bit and the output from snapshot works fine. If you need the dumps, I would be happy to send it to your email.

Thanks!

@0vercl0k
Copy link
Owner

0vercl0k commented Jul 25, 2024 via email

@0vercl0k
Copy link
Owner

Ok taking a look..

@0vercl0k
Copy link
Owner

Okay this should be fixed in v0.2.2, let me know if it isn't :)

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants