Printing stacktrace from ASAN crashes with a segfault in DEDUP mode when symbolication is missing.
Needless to say, this leads to very confusing crashes and behaviors, exacerbated by the fact that libFuzzer forks the process with a triggered bug, hiding the error out of sight.
This commit does not resolve the issue fully, as when libFuzzer forks the process the output is redirected into a logfile and will not be seen by the user. Yet at least it would be possible to diagnoze the issue by looking at that logfile.
Perhaps libFuzzer could check for existance of "ERROR: " string, and display it to stderr as well, but that would be tying two repositories two closely.
The "if" looks good, but the error message doesn't belong here: 1) it would be printed several times in this loop, 2) info.function isn't necessarily an indication that a symbolizer is not present/working (just one frame might be un-symbolizable). Either remove the error message, or move it to some other place (perhaps some init code where we initialize the symbolizers).