Add mod.fromoffset, mod.fromfileoffset to command language
#3704
Conversation
This file contains hidden or 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
Author
|
@mrexodia: please confirm. |
Member
|
In theory |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This function should perform the inverse of what
mod.offsetdoes: to get the virtual address from a file offset.I added it because I'm trying to get the start of the
.dataregion of an EXE.Specifically, I am trying to use the
findcommand to find a quick way to reconstruct global data that gets initialised by_inittermupon runtime (hope that doesn't raise too many questions).However, there is no way to convert a file offset (in variable form) to a virtual offset.
The following should print out the file offset.
However, the following is invalid in the command syntax: