Added A Code Region Unpacker in the Capstone disassembler library to … #104
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
…be used as a brute sort of disassembler when no other is available. Essentially an unpacker that directly calls the disassembler service on an entire CodeRegion
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.
Short draft for a CodeRegionUnpacker implemented in capstone. This should essentially treat an entire code region as 1 basic block and disassemble the entire thing without regard.
Use cases:
Performances or machine constraints.
Difficult to analyze binaries where code flow is less important than full instruction coverage(my current predicament).
Others I'm sure...
Issues:
ARM THUMB and PPC VLE switching not handled properly as that info has the potential to be on a basic block scope (not sure about VLE on this). This info is typically picked up by code flow analysis by a backend disassembler. I'm sure there are ways to fix this (maybe angr supplementation) , but out of scope for now.
Is there a way to load the capstone disassembler service, but prioritize other CodeRegionUnpackers over this one if loaded. Dependency injection things.