Updates:
Labels: -restrict-view-commit
Comment #7 on issue 27734 by sheriffbot: binutils:fuzz_readelf: Abrt with empty
stacktrace
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27734#c7
This bug has been fixed for 30 days. It has been opened to the public.
- Your friendly Sheriff
Comment #4 on issue 27734 by amo...@gmail.com: binutils:fuzz_readelf: Abrt with
empty stacktrace
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27734#c4
Pull request here https://github.com/google/oss-fuzz/pull/4945
--
You received this message because:
1. You were specifically CC'd o
Comment #3 on issue 27734 by p.ant...@catenacyber.fr: binutils:fuzz_readelf:
Abrt with empty stacktrace
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27734#c3
Thanks Alan, could you push this patch upstream ?
--
You received this message because:
1. You were specifically CC'd on the
Comment #2 on issue 27734 by amo...@gmail.com: binutils:fuzz_readelf: Abrt with
empty stacktrace
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27734#c2
If I understand correctly that the fuzzers run multiple inputs through a given
fuzzer image, then this patch should fix these random cr
