Hi,
This tool looks useful for fuzzing, but I would like to request GCOV support for everyday kernel testing, rather than fuzzing.
It'd be really amazing, and I would like to incorporate the tool into my current workflow if this feature is added.
Unlike fuzzing, when developing a new feature for the kernel, it is not relevant to track 1) which context ran a code snippet or 2) the order of execution. Instead, it's important to ensure that a given snippet is executed at all in the system.
It would be great to have something like:
$ vock --kernel-src $KERNEL_PATH --gcov <source file of interest>
…which would then show the source file and which lines are executed (possibly with nr of times executed) in a paged view, and periodically (or when the user presses a key) refresh the data while the command is running.
It doesn't need target program parameter because it's collecting data globally, and the command won't exit until the user tells the program to exit.
Hi,
This tool looks useful for fuzzing, but I would like to request GCOV support for everyday kernel testing, rather than fuzzing.
It'd be really amazing, and I would like to incorporate the tool into my current workflow if this feature is added.
Unlike fuzzing, when developing a new feature for the kernel, it is not relevant to track 1) which context ran a code snippet or 2) the order of execution. Instead, it's important to ensure that a given snippet is executed at all in the system.
It would be great to have something like:
…which would then show the source file and which lines are executed (possibly with nr of times executed) in a paged view, and periodically (or when the user presses a key) refresh the data while the command is running.
It doesn't need target program parameter because it's collecting data globally, and the command won't exit until the user tells the program to exit.