I got another problem when I use the gcov and lcov.
I use the gcov 2.6.9 patch to patch the kernel 2.6.9, and then I diable the MODVERSIONS option, and enable the gcov options in the config file. The process of compile was going smoothly, but when I startup the machine with the new compiled kernel, the system prompt lvm error messages and then kernel panic occured. I captured the error message displayed on the screen, any one can help me to resolve the problem, I want use the gcov and lcov to evaluate my test plan on 2.6.9 kernel, but I can not startup the machine with the 2.6.9 kernel enabled the gcov options. Or any on can give me some advice about how to use the gcov patch on Redhat RHEL 4 distribution. Thank you very much.
The following is the error messages displayed on screen:
Booting 'Red Hat Enterprise Linux AS (2.6.9-gcov)'
kernel direct mapping tables upto 1031bfff000 @ 8000-16000
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.6.9-gcov ro root=/dev/VolGroup00/LogVol00 rhgb quiet
[Linux-bzImage, setup=0x1400, size=0x216648]
[Linux-initrd @ 0x37e4f000, 0x1a0c3e bytes]
Booting the kernel.
Red Hat nash version 188.8.131.52 starting
ERROR: /bin/lvm exited abnormally! (pid 246)
ERROR: /bin/lvm exited abnormally! (pid 247)
mount: error 6 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
在2007-04-10，"Peter Oberparleiter" <email@example.com> 写道：
> I use the lcov to capture the kernel information, but I want to capture
> the kernel information for several hours, how can I do it?
The gcov-kernel patch collects code coverage data all the time. Just run your test case longenough and after that call lcov.