Add pre-relocation SHA256 identification for debugged executables #80
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
- prints the sha256 of the pre-load executable prior to starting the debugger - adds a custom monitor command to get sha256 of the pre-load executable. solana-lldb> process plugin packet monitor executable_pre_load_sha256
hash will be stored in a file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR introduces a mechanism (popped up as necessary here - anza-xyz/agave#8407 (comment)) to identify which Solana program is being debugged by:
solana-lldb> process plugin packet monitor executable_pre_load_sha256These changes make it easier for users to verify which Solana program is about to be debugged and perform any necessary target setup in
solana-lldbprior to invokinggdb-remote(target must be known before connecting to the remote end). With this PR it is now possible since the hash is displayed early in the debugging session via a message printed tostderr. The hash can also be retrieved at any time through the custom monitor command.