Once the fuzzer starts finding bugs, click on “All Findings” on the top left corner of the dashboard sidebar menu to get to the list of all findings that have been found so far.
Here, you will be able to follow bugs and vulnerabilities in your project.
Clicking on one of these will open a detailed overview of the finding, with further information on the severity of the bug and useful resources regarding the type of bug.
To inspect the bug, CI Fuzz offers fuzzing debug functionality. To debug the erroneous code with the fuzzing input that caused the crash, simply click on the “Debug” button on the top right of the Bug Detail View. This will open VS Code’s integrated debugger on the fuzz target and load the input that caused the crash. With this functionality, you are able to interactively replay what the fuzzer did and easily understand why the code is buggy.
Read next: Reproducing C/C++ Bugs