You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to have gcov output for generating test coverage results and for general informational purpose. Supporting this in a running kernel will require some output channel over which gcov report files can be generated. Generally, I can see the following path for this:
add -coverage flag to the flags for clang and gcc when we wan't to generate code coverage support
add a build option in Kconfig for using gcov
add runtime hooks for gcov (see here and search for gcov in the linux source tree (e.g. kernel/gcov/base.c))
output gcov data over the qemu debug device using the debugcon=xxx flag
build a tool to parse and separate the output from QEMU into gcov files
integrate gcov output into CI tool (.travis.yaml)
The text was updated successfully, but these errors were encountered:
I'm trying to get into OSS dev, particularly C in order to improve my knowledge of said language. I would describe myself as a beginner in C (10+ years in JS, PHP, various languages like Go, Scala, Java and Python). So I was thinking to give this issue a go. It seems to cover a good amount different tasks that need to be integrated (also I've never written or run unit tests for C so that will be new too). Mind if I have a go (and bug you or anyone else for assistance if I get hopelessly stuck?)?
It would be great to have gcov output for generating test coverage results and for general informational purpose. Supporting this in a running kernel will require some output channel over which gcov report files can be generated. Generally, I can see the following path for this:
-coverage
flag to the flags forclang
andgcc
when we wan't to generate code coverage supportKconfig
for usinggcov
gcov
(see here and search forgcov
in the linux source tree (e.g.kernel/gcov/base.c
))gcov
data over theqemu
debug device using thedebugcon=xxx
flag.travis.yaml
)The text was updated successfully, but these errors were encountered: