CLI11 Fuzzing #846
CLI11 Fuzzing #846
Conversation
|
May have opened a bit of black hole here, this could take a while to resolve. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #846 +/- ##
=======================================
Coverage 99.45% 99.46%
=======================================
Files 18 18
Lines 4071 4083 +12
=======================================
+ Hits 4049 4061 +12
Misses 22 22
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
|
I think this is ready for initial review, squashed all the commits together to a single one. The fuzz program is by no means complete but this is a start, and it already found a couple bugs. I hope to keep expanding it but I think getting it into the main branch will be good, and a place to build on. With the eventual aim to get it into OSS-Fuzz. |
|
Okay. The copyright lines at the top are a bit inconsistent; some of them are the original header, some are LL, and some don't have one at all. |
|
I will clean up the copyright, next time I work on this, probably sometime this weekend. |
…e fuzzing code, a simple test, and two fixes to issues(seg faults) found by the initial round of fuzzing. It also adds a few tests and coverage issues uncovered in the process of developing the fuzz tests. As a side effect adjusts some of the azure tests to specify the vmImage which was being changed on azure.
github-actions
bot
added
needs changelog
This PR adds the start of a fuzzing system for CLI11. It currently includes 1 issue fix found by fuzzing so I want to get it merged so we can continue to expand on it.
At some point I think it would worthwhile to try to get into OSS-Fuzz for CLI11 since it lies at the front end of an increasingly large number of projects given by the # of stars.