Issues
- 1
ConsumeRemainingBytes and ConsumeRemainingBytesAsString should invalidate further usages
#102 opened by oggy22 - 2
clang: error: unsupported option '-fsanitize=fuzzer' for target 'x86_64-w64-windows-gnu'
#104 opened by Youpen-y - 15
Code coverage metrics for libFuzzer
#41 opened by JulianVolodia - 0
We are noticing that Code Coverage is reducing suddenly - Any Clues on why would this happen?
#108 opened by rphanu - 0
Crash File Empty
#101 opened by Savitar407 - 3
- 4
[question] Continue after crash
#91 opened by SweetVishnya - 0
[Question] Remove mutations printed information
#90 opened by illera88 - 1
- 5
Crash on fuzz_me example
#26 opened by KORuL - 1
- 0
Running libfuzzer with /MD on Windows & MSVC is using incontrollable memory consumption?
#84 opened by rajeemm - 8
Libfuzzer shows issues with no error message
#81 opened by akhikolla - 0
Running fuzz test on a sample C++ project
#79 opened by ashima15448 - 1
- 1
fuzz_me.cc no error with -O1
#74 opened by pobv - 1
Libfuzzer Time complexity
#67 opened by fatimahkj - 5
After calling FDP::ConsumeRandomLengthString, remaining bytes will never start with '\'
#45 opened by nwellnhof - 0
Python script as fuzz target?
#43 opened by zhoulaifu - 3
How to use libFuzzer to test GUI applications
#20 opened by NikParam42 - 6
Is PR with fuzz target finding unpatched bugs soon after start isn't responsible disclosure?
#37 opened by JulianVolodia - 2
- 1
AFLPlusPlus Questionmark
#23 opened by domenukk - 2
- 2
How can I capture a crash in dynamic library?
#24 opened by lunexnocty - 2
Best practise: error indication
#19 opened by weinrank - 1
- 0