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.

Sign up for GitHub

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

Jump to bottom

PE: Treat the frame that was interrupted by a Win32 exception as a "first frame" (e.g. handle prologues/epilogues) #30

Open
mstange opened this issue Mar 14, 2024 · 0 comments
Open

PE: Treat the frame that was interrupted by a Win32 exception as a "first frame" (e.g. handle prologues/epilogues) #30

mstange opened this issue Mar 14, 2024 · 0 comments

Comments

@mstange
Copy link
Owner

mstange commented Mar 14, 2024

From #22:

There are no signals on Win32, but access violation exceptions work similarly. These will push a KiUserExceptionDispatcher entry on stack along with a MACHFRAME entry. We should make sure to treat anything beyond a MACHFRAME entry as the same as a first frame.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mstange