On Wed, 2004-03-10 at 15:42, Stas Bekman wrote:
rbb is back to the game and he brings gcov (test coverage) for the apr test suite: http://apr.apache.org/coverage/index.html I wonder if we could/should to do the same for mp2.
http://gozer.ectoplasm.org/mod_perl/coverage/report.html
Thanks, Philippe! Looks like we have a pretty good coverage.
For those entries which are reported to be not very well covered, it's not necessarily true, since 'make test' will exercise different parts of the code depending on the used Perl. I wonder if it's possible to run the test suite under several builds (5.6.1, 5.6.1-ithread, 5.8.3, 5.8.3-ithread) and then merge the results.
Another things that I'd like to get working is valgrind. It doesn't quite work with Apache, as it reports too many problems before it ever reaches mod_perl. Someone mentioned that it's possible to use special valgrind defines
to bracket where it should start working, allowing us to bypass Apache. I didn't have a chance to try that, yet.
Yeah, there has been a few things I've been wanting to play around with for improving mod_perl developemnt:
+ valgrind + gcov + gprof + lxr + tinderbox combining those
I'd rather try and spend my mod_perl time actually coding, but if having these kind of tools/reports can make life easier for more people than just me, I don't mind building the tools needed.
Agreed, most of these are all nice-to-have things and not very urgent. The only nice-to-have-now thing is valgrind as it sometimes helps to pinpoint memory related bugs.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
