As of now, AFL_DEBUG_CHILD enables unicorn debugging messages in the child process.
If one uses debug prints in the unicorn harness, this may easily lead to confusion, as a lot of messages about translations would be printed as well.
This PR adds an additional AFL_DEBUG_UNICORN env variable to toggle whether this translation output shall be printed as well, or not.
Probably, minor changes to AFL++ are needed as well, to surpress:
[!] WARNING: Mistyped AFL environment variable: AFL_DEBUG_UNICORN=1
Did you mean AFL_DEBUG?
Besides this, I also added some documentation about this logging differences in the README.md
As of now,
AFL_DEBUG_CHILD
enables unicorn debugging messages in the child process. If one uses debug prints in the unicorn harness, this may easily lead to confusion, as a lot of messages about translations would be printed as well.This PR adds an additional
AFL_DEBUG_UNICORN
env variable to toggle whether this translation output shall be printed as well, or not. Probably, minor changes to AFL++ are needed as well, to surpress:Besides this, I also added some documentation about this logging differences in the README.md