Hi list
I'm having some technical problems with embperl. When apache2 handles a
second request, the child dies with segmentation fault. The first
request is processed fine. I was able to do a backtrace using gdb and
httpd -X (the signal handler shown in #3 was installed by me to handle
SIGSEGV):
Am 20.09.2005 um 11:58 schrieb Alvaro Lopes:
Hi list
I'm having some technical problems with embperl. When apache2
handles a
second request, the child dies with segmentation fault. The first
request is processed fine. I was able to do a backtrace using gdb and
httpd -X (the signal handler s
>
> Version of embperl is 2.0.0, mod_perl 2.0.1, apache 2.0.54
> (prefork mpm only), perl 5.8.4.
>
> Any ideas ?
>
How does your httpd.conf look like?
Did you load the C part with LoadModule and the Perl part (with PerlModule
or use) both on startup?
Gerald
Gerald Richter wrote:
>>Version of embperl is 2.0.0, mod_perl 2.0.1, apache 2.0.54
>>(prefork mpm only), perl 5.8.4.
>>
>>Any ideas ?
>>
>
>
> How does your httpd.conf look like?
>
> Did you load the C part with LoadModule and the Perl part (with PerlModule
> or use) both on startup?
using Per
>
> Gerald Richter wrote:
> >>Version of embperl is 2.0.0, mod_perl 2.0.1, apache 2.0.54 (prefork
> >>mpm only), perl 5.8.4.
> >>
> >>Any ideas ?
> >>
> >
> >
> > How does your httpd.conf look like?
> >
> > Did you load the C part with LoadModule and the Perl part (with
> > PerlModule or use)
Gerald Richter wrote:
Ok - I've done that. The SES: message always comes from the
parent process so it is not always easy to match the SESSION
data to the child process that is actually performing the request.
The question is, what are you seeing in case of the problem you have. Could
> The problem seems directly attributable to a 500
> configuration error occuring with a request that was using
> the session. These configuration errors were occuring
> because of an error in our code which was causing Storable to
> fail. It seems like the next connection to a process that
