-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Show File Offset for Currently Selected Address #154
Comments
Currently there is nothing built-in to do this. The file offset to memory address mapping is lost during import. You would have to write a script to figure out the file offset, which would be specific to your binary's file format. |
@ryanmkurtz is this something that may be added in a future release? |
I have switched this over to an enhancement so we can consider it for a future release. |
@ryanmkurtz cool :) |
@ryanmkurtz was this implemented in v9.0.1? |
@OothecaPickle, no, it was not implemented for the patch release. |
This has been implemented for 9.1. You can test it out in the master branch. |
great :) |
Hym, I don't see where the data are displayed. Can you help me with this? |
You have to hover on an address in the listing. There's also a new field in the Memory Map to show where each memory block was mapped from in the file. |
@ryanmkurtz is this available in the Ghidra API? i.e. converting an address to it's file offset? |
Yes. From |
Is there a way to "Goto" the file offset's equivalent address? |
…uments to formatting function Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Fix code scanning alert NationalSecurityAgency#154: Wrong type of arguments to formatting function
Is there a way to get Ghidra to always show the *file offset (in hex) for the currently selected address somewhere?
The text was updated successfully, but these errors were encountered: