Nathan Byrd wrote:
Actually, it was easier than I thought to come up with a stripped down
version - it can be done without Apache::PAR or PAR at all - it appears
to be happening with any PerlModule coming from an add_config(). The
following code generates the same segfault for me:
In startup.pl:
Nathan Byrd wrote:
I'm sorry, I was looking at the wrong line. I'm not using Apache::compat
for Apache::PAR (figured it would be bad form.) The line it's using
(for mod_perl 2.x) is:
$err = Apache->server->add_config([split /\n/, $conf]);
cool
> Actually, it was easier than I thought to come up
On Sat, 2003-03-22 at 23:14, Stas Bekman wrote:
[snip]
>
> Any chance you can come up with a stripped version of Apache::PAR that still
> reproduces the problem? So we can have a good test?
>
> If not, where do I get the version of Apache::PAR that you are having the
> problem with?
>
Actuall
On Sat, 2003-03-22 at 23:14, Stas Bekman wrote:
> Nathan Byrd wrote:
> > Hi all,
> >
> > I have been getting a segfault when starting mod_perl 2.x under rather
> > unusual circumstances. Hopefully the below bug report will be useful,
> > although I'm not sure whether the problem lies in mod_perl
Nathan Byrd wrote:
Hi all,
I have been getting a segfault when starting mod_perl 2.x under rather
unusual circumstances. Hopefully the below bug report will be useful,
although I'm not sure whether the problem lies in mod_perl 2.x or PAR.pm
(a CPAN module), but since the entire trace from debuggi
