Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
A few days ago, we tried to patch our kernel (2.6.10-rc3-mips) with =
Then. enable the option "Include GCOV coverage profiling" and "Provide =
GCOV proc file system entry" so that gcov-core.o and gcov-proc.o are =
built in the kernel image.
The compiler flag "-fprofile-arcs -ftest-coverage" is added in proper =
way, and the .bb and .bbg related files are also generated after making =
Then, after a system booting, we can see the message "gcov-core: core =
init gcov-proc: proc init (persist=3D0 link=3D1)" shown.=20
However, we only can see one vmlinux under /proc/gcov. Why we cannot get =
any .da files?
Is there something wrong ?
Could you give us some suggestion?
From: Peter Oberparleiter <oberparleiter@go...> - 2006-07-06 07:54:45
Chuck Chen wrote:
> Then. enable the option "Include GCOV coverage profiling" and "Provide
> GCOV proc file system entry" so that gcov-core.o and gcov-proc.o are
> built in the kernel image.
Did you also enable CONFIG_GCOV_ALL? If not then this is the reason why you are only seeing a single file in /proc/gcov.