From: Jarod W. <ja...@wi...> - 2006-03-31 01:53:23
|
Hey all, Anyone out there have experience working with a gcov-patched Red Hat=20 Enterprise Linux 4-based kernel? I'm trying to figure out just how all this= =20 works... So far, I've got the gcov 2.6.9 patch integrated into a kernel rpm build wi= th=20 the requisite extra options enabled and MODVERSIONS disabled, so I'm now=20 getting a ton of stuff dumped into /proc/gcov/* (i.e., .h, .c and .gcno=20 symlinks back to the kernel source tree and .gcda files), but something sti= ll=20 doesn't appear to be quite right. Even after running through a battery of=20 tests, an 'lcov -c -o outputfile' results in an outputfile with nothing but= a=20 bunch of lines reading... 'TN:' =2E..and nothing more. Any clues? I've seen hits in the mailing list archive about how lcov won't= =20 work on SLES9 kernels, but didn't see anything RHEL4-specific... Am I missi= ng=20 something obvious here? Thanks much for any help anyone can provide. In the interim, I'm going to see what happens w/a vanilla kernel... =2D-=20 Jarod Wilson ja...@wi... |
From: Jarod W. <ja...@wi...> - 2006-03-31 05:01:56
|
On Thursday 30 March 2006 17:50, Jarod Wilson wrote: > Anyone out there have experience working with a gcov-patched Red Hat > Enterprise Linux 4-based kernel? I'm trying to figure out just how all th= is > works... > > So far, I've got the gcov 2.6.9 patch integrated into a kernel rpm build > with the requisite extra options enabled and MODVERSIONS disabled, so I'm > now getting a ton of stuff dumped into /proc/gcov/* (i.e., .h, .c and .gc= no > symlinks back to the kernel source tree and .gcda files), but something > still doesn't appear to be quite right. Even after running through a > battery of tests, an 'lcov -c -o outputfile' results in an outputfile with > nothing but a bunch of lines reading... > > 'TN:' > > ...and nothing more. > > Any clues? I've seen hits in the mailing list archive about how lcov won't > work on SLES9 kernels, but didn't see anything RHEL4-specific... Am I > missing something obvious here? > > Thanks much for any help anyone can provide. > > In the interim, I'm going to see what happens w/a vanilla kernel... Blah. Everything works perfectly w/a vanilla 2.6.15. Time to start hacking = out=20 Red Hat patches? Anyone have an idea what might be the culprit here? =2D-=20 Jarod Wilson ja...@wi... |