[llvm-bugs] [Bug 46468] New: LibFuzzer exits with code 77
via llvm-bugs
llvm-bugs at lists.llvm.org
Fri Jun 26 09:05:00 PDT 2020
https://bugs.llvm.org/show_bug.cgi?id=46468
Bug ID: 46468
Summary: LibFuzzer exits with code 77
Product: compiler-rt
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: fuzzer
Assignee: unassignedbugs at nondot.org
Reporter: cem.f.karan.civ at mail.mil
CC: llvm-bugs at lists.llvm.org
I'm using LibFuzzer via bolero. The related bug on that project is
[here](https://github.com/camshaft/bolero/issues/18).
When I run bolero, I get the following:
```bash
cargo bolero fuzz -t 100sec communications::messages::message::tests::merge
Finished test [unoptimized + debuginfo] target(s) in 0.07s
running 1 test
WARNING: Failed to find function "__sanitizer_acquire_crash_state".
WARNING: Failed to find function "__sanitizer_print_stack_trace".
WARNING: Failed to find function "__sanitizer_set_death_callback".
INFO: Seed: 1089555166
INFO: Loaded 1 modules (1159931 inline 8-bit counters): 1159931
[0x5600931efe00, 0x56009330b0fb),
INFO: Loaded 1 PC tables (1159931 PCs): 1159931
[0x56009330b100,0x5600944be0b0),
INFO: 1663 files found in
/home/cfkaran2/Documents/repositories/bit_network/bit_network_library/src/communications/messages/__fuzz__/communications__messages__message__tests__merge/corpus
INFO: -max_len is not provided; libFuzzer will not generate inputs larger than
4096 bytes
INFO: seed corpus: files: 1663 min: 1b max: 1617b total: 672085b rss: 84Mb
#1664 INITED cov: 7151 ft: 29966 corp: 535/164Kb exec/s: 832 rss: 95Mb
#1916 NEW cov: 7151 ft: 29971 corp: 536/166Kb lim: 1577 exec/s: 638 rss:
95Mb L: 1511/1567 MS: 2 ChangeASCIIInt-ChangeBit-
#2008 REDUCE cov: 7151 ft: 29971 corp: 536/166Kb lim: 1577 exec/s: 669 rss:
95Mb L: 875/1567 MS: 2 ChangeBinInt-EraseBytes-
#2048 pulse cov: 7151 ft: 29971 corp: 536/166Kb lim: 1577 exec/s: 682 rss:
95Mb
#2225 NEW cov: 7151 ft: 29979 corp: 537/166Kb lim: 1577 exec/s: 741 rss:
95Mb L: 152/1567 MS: 2 ChangeBit-ChangeBit-
F
failures:
failures:
communications::messages::message::tests::merge
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 353 filtered
out
==30473== ERROR: libFuzzer: fuzz target exited
SUMMARY: libFuzzer: fuzz target exited
MS: 2 InsertByte-ChangeByte-; base unit:
a5cab92cdd25d4d8fbe849e1c08cf3c9da97daec
artifact_prefix='/home/cfkaran2/Documents/repositories/bit_network/bit_network_library/src/communications/messages/__fuzz__/communications__messages__message__tests__merge/crashes/';
Test unit written to
/home/cfkaran2/Documents/repositories/bit_network/bit_network_library/src/communications/messages/__fuzz__/communications__messages__message__tests__merge/crashes/crash-b90311f056ed895f4fd4ab9374f090e292023fa6
error: process exited with status 77
```
Bolero doesn't have such an exit number, and neither does my own code. The
only exit code I found that matched came from within LibFuzzer, and it
indicates an internal error. Is there anything I can do to give you a better
bug report than this?
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200626/e93f29d8/attachment.html>
More information about the llvm-bugs
mailing list