KCOV is aware of the order in which coverage is collected. Using this data, it should be possible to capture and visualize the sequence of kernel code execution triggered by a series of actions in the target program.
This would provide developers and researchers with deeper insights into the execution flow, rather than only knowing which lines or functions were covered. Such a visualization could be useful for:
- Understanding complex kernel execution paths
- Debugging subtle ordering-related bugs
- Enhancing fuzzing feedback with execution trace context.
KCOV is aware of the order in which coverage is collected. Using this data, it should be possible to capture and visualize the sequence of kernel code execution triggered by a series of actions in the target program.
This would provide developers and researchers with deeper insights into the execution flow, rather than only knowing which lines or functions were covered. Such a visualization could be useful for: