On 18/08/09 02:30 , James Smith wrote:
>
> Phillipe,
>
> Thnx, that seems to have solved the problem - I'd been slurping in the
> page template file with a $/..
In theory, if you used local $/, it should work, maybe.
Can you try this small patch ?
Index: src/modules/perl/modperl_perl_global.c
Phillipe,
Thnx, that seems to have solved the problem - I'd been slurping in the
page template file with a $/.. it also explains why switching from
using perl-script to modperl as the handler type also resolved the
issue...
James
On Tue, 18 Aug 2009, Philippe M. Chiasson wrote:
On 17/08/0
On 17/08/09 21:48 , Philippe M. Chiasson wrote:
> On 17/08/09 19:54 , James Smith wrote:
>>
>> Futher to this I now have a stack trace if that helps anyone point me in
>> the right direction:
>>
>> #0 0x7f17ee936fb1 in strncpy () from /lib/libc.so.6
>> #1 0x7f17e808ecfc in modperl_perl_gl
On 17/08/09 19:54 , James Smith wrote:
>
> Futher to this I now have a stack trace if that helps anyone point me in
> the right direction:
>
> #0 0x7f17ee936fb1 in strncpy () from /lib/libc.so.6
> #1 0x7f17e808ecfc in modperl_perl_global_request_save () from
> /usr/lib/apache2/modules
Futher to this I now have a stack trace if that helps anyone point me in
the right direction:
#0 0x7f17ee936fb1 in strncpy () from /lib/libc.so.6
#1 0x7f17e808ecfc in modperl_perl_global_request_save () from
/usr/lib/apache2/modules/mod_perl.so
#2 0x7f17e807dabc in modperl_respo
I have two handlers, one a response handler and a second an output filter.
If either of these handlers run then they run fine for any number of
requests, if I have both of these handlers I get an untraceable seg fault
with the handlers, this segfault happens on the second request to that
partic
