On Mon, Feb 03, 2003 at 11:16:25AM -0600, Hann, Brian wrote:
> I wish that was an option, but unfortunately it's not due to the extreme
> amount of applications we would have to test and we don't have the
> manpower or time for that.
of course, by posting to this list, you have just made any would
few more things and then
I'll post the results.
Brian
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 03, 2003 11:00 AM
To: Hann, Brian
Cc: [EMAIL PROTECTED]
Subject: Re: coredump with 3 PerlSetVars
Apache 1.3.6 is ancient, has num
Apache 1.3.6 is ancient, has numerous known bugs and security exploits.
Same for mod_perl 1.21.
Update to apache 1.3.27 and I think mod_perl 1.27, see if it still happens.
Wes
"Hann, Brian" <[EMAIL PROTECTED]> on 02/03/2003 11:43:23 AM
To:<[EMAIL PROTECTED]>
cc:
Subject:coredump with
Thanks a lot, i knew gdb was what I should be using, but I've never had to use
it so the uptake was a bit slow. Here is the stack trace:
#0 0x4007b105 in SSL_CTX_ctrl ()
#1 0x8083500 in ssl_init_Module ()
#2 0x8083827 in ssl_init_Module ()
#3 0x80b49a9 in ap_init_modules ()
#4 0x80be4e5 in ap
Try analyzing the core files with GDB do something like
#gdb -c /usr/sbin/httpd
then, at the "(gdb)" prompt, type "where" - this would give you a stack
backtrace from the point it cored.
-Original Message-
From: Dana Powers <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]
The newsgroup comp.infosystems.www.servers.unix is the usual hangout for
Apache-related issues...
-Alan
-Original Message-
From: Dana Powers <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, July 14, 2000 3:39 PM
Subject: Coredump
>Do any of you know a better p
