Repository navigation
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
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.
New
bytes-maskedModeRadare2 v6.0.0 introduced a new command
p8fmj. This provides not only a function's raw bytes but some additional information as follows:This PR introduces
bytes-maskedmode. This works exactly as the bytes mode, except that it uses thep8fmcommand to extract the a bit-level mask and applies the mask to the function raw bytes with a logic AND operation. The result is stored alongside each function's raw bytes in a separate file with extension.masked.bin.Hence, for a function named
entry0, the output ofbin2ml extracton a binary file namedtest_binwill be the following:Improved Error Handling
Previously, even though raw bytes would be extracted function-by-function, it could happen that an error would be encountered on a single function, which would abort the entire scan.
For example, a binary with >35k functions could contain a single faulty function leading to an error. That error would abort the scan and also discard all the data extracted until that point.
This commit changes that with function-level error handling. If an error is encountered for a function named
entry0, the error message will be stored intest_bin-bytes/entry0.error.logand the scan will continue until the end.