We are trying to use Devel::Cover module and "cover" in our regression tests run to generate product code coverage data. However, we met two big problems:
(1) Lots of our perl test scripts failed in code coverage run and seems related to B::Deparse and we got million lines of messages like below in our logs: ---- Deep recursion on subroutine "B::Deparse::find_scope" at ....../glibc-2.3.4/x86_64/perl/....../lib/5.8.8/x86_64-linux-thread-multi/B/Deparse.pm line 1321. B::Deparse: .../glibc-2.3.4/x86_64/perl/ .../lib/5.8.8/x86_64-linux-thread-multi/B/Deparse.pm:1309 called B::Deparse::find_scope --- Those failed tests would pass if we did not use Devel::Cover. Any clue for these B::Deparse messages will be very helpful for us. (2) Because we used Devel::Cover to fully instrument all our perl scripts and modules of our product in full regression run, the generated coverage data set (in cover_db) was very huge. So, when we ran "cover" to merge coverage data and generate final code coverage report, "cover" ran out of memory and the "cover" process was killed in the middle. Any experience and suggestion on how to deal with running "cover" to merge huge data set to avoid crash for running out of memory? I think there must be some other folks use Devel::Cover in the scale like us, so we appreciate your information and comments. Thanks in advance! Scott __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
