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.
Fix issue where radare2 did not send output to 'fuzz_radare' when running
Fix false positives due to first line of 'fuzz_gdb' being different for each file no matter what
Combine both
tail
commands into one to make the output more readableCommands to run to install r2pipe module needed for the fix :
When I followed your tutorial, I realized that
fuzz.py
gave me way too many false positive. I investigated and found that it was becausegdb
always printed a line with 'Loading symbols from [path/to/file]'. The new command runs gdb in batch mode and execute commands via-ex
parameter and the problem is gone.Another thing that gave me false positive was the content of
fuzz_radare
. It was always empty so every time it compared it withorig_radare
, it says that it was different. To fix it, I installed ther2pipe
module and adapted the code to make it work. Online forums recommended that module to run radare2 commands in python scripts.Everything now works correctly and there are a lot less false positive.
Versions info