Are you running Apache 2.0 on Windows?
Tyler Bird wrote:
Hi all,
I was wondering how I could use the %SIG has to catch a segmentation
fault.
I am setting up a new server with mod_perl + apache 2.0 + some legacy
code
and am sporadically rececing a segmentation fault to my apache logs
like s
Hi all,
I was wondering how I could use the %SIG has to catch a segmentation fault.
I am setting up a new server with mod_perl + apache 2.0 + some legacy code
and am sporadically rececing a segmentation fault to my apache logs like so.
child pid 15077 exit signal Segmentation fault (11)
%SIG{'
Hi,
Installed a fresh FreeBSD 5.5-R-p12 (I *NEED* to run
5.5, sorry) with :
apache+mod_ssl+mod_deflate-1.3.37+2.8.28
perl-threaded-5.8.8
mod_perl-1.30
all installed via the FreeBSD ports collection.
When I try to start it I get a segfault. The backtrace is :
(gdb) bt
#
Am Mittwoch, 16. Mai 2007 16:39 schrieb Joel Bernstein:
> On Wed, May 16, 2007 at 03:28:17PM +0200, Moritz Maisel wrote:
> > Running Debian:
> > libapache2-mod-perl21.999.21-1
> > Integration of perl with the Apache2 web server
>
> So you're running an alpha
On Wed, May 16, 2007 at 03:28:17PM +0200, Moritz Maisel wrote:
> Running Debian:
> libapache2-mod-perl21.999.21-1
> Integration of perl with the Apache2 web server
So you're running an alpha release of mod_perl 2, with 21 levels of
backported patches? Try up
2007/5/15, Adam Prime x443 <[EMAIL PROTECTED]>:
use Apache::RequestRec;
?
I use "Apache::RequestRec" to have access to the object method "user" in the
line:
my $user = $r->user;
What version of mod_perl are you running? The above line makes me thing
you're running an reall old version of m
