From: Peter Oberparleiter <oberparleiter@go...> - 2006-05-16 16:51:22
Unrein, Jason wrote:
> Is there an active gcov mailing list? I'm trying to find some help with
> an issue.
Note that there's a difference between gcov (tool part of GCC) and gcov-kernel (the kernel patch that allows to collect gcov-compatible data). You're most likely interested in the latter. The relevant mailing list would be: ltp-coverage@...
> I have seen numerous ports online about people having issues with gcov
> unresolved symbols and "Linux/modversions.h" not existing but I have not
> seen a solution for either problem.
I usually reply to gcov-kernel related questions on ltp-coverage and only recently subscribed to ltp-list (didn't get your inital message though until forwarded by Nigel).
> Basically, when I compile gcov into their the vanilla 2.6.9 or 2.6.11
> kernel, it complains about "linux/modversions.h" not existing. If I
> either comment out that #include or do a symbolic link to
> /include/config/modversions.h, I can compile but the linker complains
> about __gcov_* functions being undefined.
Most of the gcov-kernel patch versions found in the files section of the LTP project site are outdated. You can get the most recent gcov-kernel patch code from anonymous CVS:
Note that there are no updated versions for kernel 2.6.9 or 2.6.11. If you need gcov-kernel support for these levels, please try applying one of the patches for another version.
The modversions.h-problem should be fixed with the updated patch. The __gcov_init-linker problems should also be addressed. Depending on the compiler you're using, you may need to enable CONFIG_GCOV_HAMMER (e.g. for Novell's SLES compiler).
Hope this helps.