Add PANDA API to inject page faults for i386 and mips #1103
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AndrewFasano
force-pushed
the
feat/pagefault
branch
2 times, most recently
from
54cc882
to
97aa183
Compare
AndrewFasano
force-pushed
the
feat/pagefault
branch
from
20518ca
to
de1b7fe
Compare
AndrewFasano
force-pushed
the
feat/pagefault
branch
from
de1b7fe
to
8823ced
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a
panda_virtual_memory_...function fails due to paged out memory,panda_page_fault()allows you to force the guest to page in that memory and return execution to a PC of your choice (typically the same PC you were at before).Using this as a fallback for when memory is unavailable requires some intentional design of your analysis code - if you identify that memory is unavailable, you should request the page fault, bail, and then have your analysis restart after the page fault is resolved. With
syscalls2based callbacks, this is easy as you will get theon_sys_...callback again after the fault is resolved. In other situations, it may be more difficult.