Support "embedding" libbs in Ghidra Context #168
Merged
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
# Conflicts: # libbs/decompilers/ghidra/interface.py
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 allows constructing a
GhidraDecompilerInterfacefrom within Python code that is run inside a Ghidra Script context, e.g. a Python3-postscriptexecuted with PyGhidra.My use case for this is that some code can easily be tested by running it as Script within an already running Ghidra Instance (either Headless or GUI), which can then also be reloaded and re-run without having to restart Ghidra.
As far as I understood the interface code there is no assumption that requires
libbsto start Ghidra itself, it just needs aProgramto work with, and as long as the caller provides this, it could now be used.