Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> > segfaults for me in the test suite. Running the server under gdb
> > indicates the segfault is happening during loading of B::Deparse on
> > this line in the test-
> > $r->add_output_filter("out_filter");
>
> And if you add it at the startup, it happens too. I think it tries to
> deparse out_filter as a code string, instead of trying to get the code
> reference.
Oops, sorry- I think I made a mistake about the failing line...
I think it's really the next one that segfaults:
# test adding anon sub
$r->add_output_filter(sub {
my $filter = shift;
while ($filter->read(my $buffer, 1024)) {
$buffer .= "end";
$filter->print($buffer);
}
return Apache::OK;
});
mod_perl is trying to deparse the anonymous sub, and it needs
B::Deparse for that. (I'm still trying to grok the necessity/safety
of the deparse.)
FWIW, the backtrace I get is identical to the one Joe Orton posted.
Lately I been finding it easier to get proper backtraces from the
worker mpm by running the tests under gdb (nicely explained in
docs/devel/debug/c.pod) instead of trying to examine the core file.
--
Joe Schaefer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
