Add gdb scripts for memquery and drsymload #4505
Merged
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
Adds two gdb python scripts I've developed that may be useful to others: 1) drsymload: loads DR symbols regardless of gdb's current state, which may include having DR symbols at the wrong address. It does this by reading /proc/self/maps and running objdump on libdynamorio.so. Ideally this would be integrated into a revived libdynamorio.so-gdb.py: that's part of #2100. 2) memquery: prints the /proc/self/maps line for a given address. I'm still shocked gdb doesn't provide such a command natively. Issue: #2100
abhinav92003
approved these changes
Oct 30, 2020
|
I updated https://github.com/DynamoRIO/dynamorio/wiki/Debugging to point to these. |
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.
Adds two gdb python scripts I've developed that may be useful to others:
drsymload: loads DR symbols regardless of gdb's current state,
which may include having DR symbols at the wrong address. It does
this by reading /proc/self/maps and running objdump on
libdynamorio.so. Ideally this would be integrated into a revived
libdynamorio.so-gdb.py: that's part of tools/libdynamorio.so-gdb.py causes "RuntimeError: Cannot access memory at address 0x712fd867" #2100.
memquery: prints the /proc/self/maps line for a given address.
I'm still shocked gdb doesn't provide such a command natively.
Issue: #2100