-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
Thanks a lot - I'm going to investigate that this week!
If you do have a dump that'd be helpful to accelerate my investigation :)
Cheers
…On Wed, Jul 24, 2024 at 8:19 PM Duc Phan ***@***.***> wrote:
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!
—
Reply to this email directly, view it on GitHub
<#8>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALIORMWHN327NC4J7MC3QLZOBVFJAVCNFSM6AAAAABLNVFLU6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDQOBZGE3DCOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ok taking a look.. |
Okay this should be fixed in Cheers |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
, thelimit
was0xffffffff
in bdump and0xfffff
in snapshot. Changing these values in snapshot'sregs.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!
The text was updated successfully, but these errors were encountered: