-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging issue in gnutls_idna_parser_fuzzer #417
Comments
@alex, I would like to assign this to you, but cannot :) |
CC @nmav who wrote that fuzzer. |
Done |
Is there a way for us to force rebuild? |
see request in: google/oss-fuzz#417 Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
No, sorry no way to force rebuild, filed #419. |
@nmav - can you look at the last failure. |
@inferno-chromium I've committed a fix to include string.h. |
Thanks for the fixes, I've kicked off the next build manually. |
One more error:
|
Updated. |
Cool, now build is successful, thanks @nmav ! Though it is marked as UNSTABLE due to crashes which are easy to find (https://oss-fuzz-build-logs.storage.googleapis.com/status.html). All those crashes should have been already automatically filed in the bug tracker, or they will be filed soon :) |
Can this be closed now? |
It is now crashing 100% of the time on the assert added See https://oss-fuzz.com/v2/testcase-detail/6049131028021248 and https://oss-fuzz.com/v2/performance-report/libFuzzer_gnutls_idna_parser_fuzzer/libfuzzer_asan_gnutls/latest |
Why is that happening marked as reproducible: no, if it's 100%? (I didn't see it because I only follow the issue tracker) |
I couldn't reproduce that locally, need to debug more. |
Something has fixed this, the issue is now gone - https://oss-fuzz.com/v2/performance-report/libFuzzer_gnutls_idna_parser_fuzzer/libfuzzer_asan_gnutls/latest. |
If you take a look at performance report for gnutls_idna_parser_fuzzer: https://oss-fuzz.com/v2/performance-report/libFuzzer_gnutls_idna_parser_fuzzer/libfuzzer_asan_gnutls/latest
You'll see that it suffers a lot from startup_crash issue. Actually, there is a logging issue due to
printf
being called for (almost?) every input: https://gitlab.com/gnutls/gnutls/blob/master/devel/fuzz/gnutls_idna_parser_fuzzer.cc#L34Could you please remove that
printf
from fuzz target or ping maintainers to remove it and never add it again? :)Regarding incorrect verdict from performance analysis, we are working on it.
The text was updated successfully, but these errors were encountered: