You can visualize test cases to better understand the context of a crash or to identify performance bottlenecks that limit the fuzzer’s throughput.
Instructions
On the Run Page, navigate to the Test Cases section. These are all the unique test cases the fuzzer has generated so far for your firmware. These are ordered in decreasing order of coverage. This means that the deepest test case will always be at the top of this table:
Clicking the Graph button for a test case opens a new window where the execution is rendered as a flame graph. The graph shows every function that has executed in your firmware from boot to the end of the test case:
The measurement unit used in the flame graph is the basic block, but you can think of it as units of computation or time. Generally, the more blocks a function has used, the more time it has used.