We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A new crash was discovered for fuzzing target mph. Here is a snippet of the log:
2019/12/23 14:30:20 downloading seed 2019/12/23 14:30:21 no seed corpus. continue... 2019/12/23 14:30:21 downloading corpus 2019/12/23 14:30:21 no generating corpus yet. continue... 2019/12/23 14:30:21 downloading fuzzer 2019/12/23 14:30:22 downloading additional corpus 2019/12/23 14:30:22 no additional-corpus. skipping... 2019/12/23 14:30:22 Running fuzzing with: ./fuzzer -print_final_stats=1 -exact_artifact_path=./artifact -error_exitcode=76 -max_total_time=3600 corpus additional-corpus seed -rss_limit_mb=1984 FUZZER: INFO: Seed: 3726776796 FUZZER: INFO: 65536 Extra Counters FUZZER: INFO: 0 files found in corpus FUZZER: INFO: 0 files found in additional-corpus FUZZER: INFO: 0 files found in seed FUZZER: INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes FUZZER: INFO: A corpus is not provided, starting from an empty corpus FUZZER: #2 INITED ft: 76 corp: 1/1b lim: 4 exec/s: 0 rss: 26Mb FUZZER: #3 NEW ft: 78 corp: 2/3b lim: 4 exec/s: 0 rss: 26Mb L: 2/2 MS: 1 InsertByte- FUZZER: #6 NEW ft: 79 corp: 3/6b lim: 4 exec/s: 0 rss: 26Mb L: 3/3 MS: 3 ChangeByte-CMP-CopyPart- DE: "\x01\x00"- FUZZER: #336 NEW ft: 80 corp: 4/9b lim: 4 exec/s: 0 rss: 26Mb L: 3/3 MS: 5 ShuffleBytes-CopyPart-ChangeBinInt-ChangeBit-EraseBytes- FUZZER: #943 REDUCE ft: 80 corp: 4/7b lim: 4 exec/s: 0 rss: 26Mb L: 1/3 MS: 2 EraseBytes-EraseBytes- FUZZER: #2954 NEW ft: 81 corp: 5/13b lim: 6 exec/s: 0 rss: 26Mb L: 6/6 MS: 1 InsertRepeatedBytes- FUZZER: #7969 NEW ft: 82 corp: 6/24b lim: 11 exec/s: 0 rss: 28Mb L: 11/11 MS: 5 EraseBytes-EraseBytes-InsertRepeatedBytes-ChangeBinInt-InsertByte- FUZZER: #17991 REDUCE ft: 134 corp: 7/45b lim: 21 exec/s: 17991 rss: 29Mb L: 21/21 MS: 2 CMP-CrossOver- DE: "\x00\x00\x00\x00"- FUZZER: ALARM: working on the last Unit for 1200 seconds FUZZER: and the timeout value is 1200 (use -timeout=N to change) FUZZER: MS: 1 ChangeByte-; base unit: e6e51fdc0572094ff3574d5b922354589890309e FUZZER: 0x0,0x0,0x5e,0xa,0x0,0x0,0x0,0xa,0xb5,0xb5,0xb4,0x4a,0xf3,0x4a,0x4a,0x4a,0x3d,0x0,0x0,0x0,0x0, FUZZER: \x00\x00^\x0a\x00\x00\x00\x0a\xb5\xb5\xb4J\xf3JJJ=\x00\x00\x00\x00 FUZZER: artifact_prefix='./'; Test unit written to ./artifact FUZZER: Base64: AABeCgAAAAq1tbRK80pKSj0AAAAA FUZZER: ==26== ERROR: libFuzzer: timeout after 1200 seconds FUZZER: #0 0x4b059f in __sanitizer_print_stack_trace /tmp/final/llvm.src/projects/compiler-rt/lib/ubsan/ubsan_diag_standalone.cc:29:3 FUZZER: #1 0x4529a8 in fuzzer::PrintStackTrace() /tmp/final/llvm.src/projects/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:206:5 FUZZER: #2 0x430c1d in fuzzer::Fuzzer::AlarmCallback() /tmp/final/llvm.src/projects/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:300:5 FUZZER: #3 0x7f80c8a9e0df (/lib/x86_64-linux-gnu/libpthread.so.0+0x110df) FUZZER: #4 0x55dc30 in github.com/suggest-go/suggest/pkg/mph.(*mph).Build /home/travis/gopath/src/github.com/suggest-go/suggest/pkg/mph/mph.go:85 FUZZER: FUZZER: SUMMARY: libFuzzer: timeout FUZZER: stat::number_of_executed_units: 17992 FUZZER: stat::average_exec_per_sec: 14 FUZZER: stat::new_units_added: 7 FUZZER: stat::slowest_unit_time_sec: 0 FUZZER: stat::peak_rss_mb: 32 2019/12/23 14:50:25 process finished with error = exit status 77 2019/12/23 14:50:25 Exit Status: 77 2019/12/23 14:50:26 uploading crash...
More details can be found here
Cheers, Fuzzit Bot
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A new crash was discovered for fuzzing target mph.
Here is a snippet of the log:
More details can be found here
Cheers,
Fuzzit Bot
The text was updated successfully, but these errors were encountered: