Hi,
On Tue, 21 Sep 2004, Kevin Scaldeferri wrote:
> This patch gets rid of that error, and now my server starts up. I
> admit that I don't really understand its magic (eval 'BEGIN{1}'???),
> but it's progress.
What you call magic actually forces perl to run function 'runops_cover'
(see Cover.xs).
> However, I seem to be having problems with stability when I run lots of
> tests (a couple thousand). After I do this, something seems unhappy in
> the internals, and when I try to kill apache, I get a bunch of this
> sort of stuff:
> ...
> ... many hundreds of lines ...
>
> and if I run 'cover', none of the coverage from my tests appears.
>
> So, I don't expect anyone to try to figure out this stack trace stuff,
> but I'm curious if other people have seen stability problems like this?
> Alternatively, if someone can tell me the exact logistics of how they
> get the coverage out in the end, I'd appreciate it. Is there another
> way than 'kill'ing the apache process to get Devel::Cover to write its
> data? It seems to do it at one point during startup, but after that it
> looks like it just stays in memory, which I end up losing when things
> go bad terminating the process.
I have not seen this error. The only thing I may suggest is restarting httpd
after sertain number of tests.
Vadim.
