Once the fuzzer starts finding bugs, they will be reported in multiple places in the UI (marked in green)
Click on “All Findings” on the top left corner of the dashboard to get to the list of all bugs that have been found so far.
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.