Skip to content

Attempt to backtrace through jit frames on x86_64 Windows #274

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

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

alexcrichton
Copy link
Member

This is being developed in conjunction with bytecodealliance/wasmtime#759 and should allow x86_64-pc-windows-* to natively backtrace through JIT frames

@alexcrichton
Copy link
Member Author

@peterhuene mind double-checking me on this?

Copy link

@peterhuene peterhuene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@yurydelendik was this change tested with tracing through JIT frames?

// dbghelp for getting the function table and module base. Instead we use
// the `RtlLookupFunctionEntry` function in kernel32 which will account for
// JIT compiler frames as well. These should be equivalent, but using
// `Rtl*` allows us to backtrace through JIT frames.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just thinking that we should perhaps mention that this is limited to in-process walking only, which is fine for backtrace's use case.

@alexcrichton alexcrichton merged commit 7a1d357 into master Jan 15, 2020
@alexcrichton alexcrichton deleted the windows-x86-64-jit branch January 15, 2020 18:54
@peterhuene
Copy link

@yurydelendik never mind, I missed the earlier comment by @alexcrichton regarding testing these changes with your PR!

@pravic
Copy link

pravic commented Feb 14, 2020

Note: This pushes the minimum Rust version to 1.38 due to cast().

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 this pull request may close these issues.

3 participants