The following reply was made to PR mod_proxy/1942; it has been noted by GNATS.

From: Marc Slemko <[EMAIL PROTECTED]>
To: Lukas Karrer <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], Apache bugs database <[EMAIL PROTECTED]>
Subject: Re: mod_proxy/1942: CONNECT Problem with SSL Proxy
Date: Tue, 17 Mar 1998 22:19:26 -0700 (MST)

 On Tue, 17 Mar 1998, Lukas Karrer wrote:
 
 > httpd writes into the logfile:
 > 
 > > [Tue Mar 17 11:48:24 1998] [notice] httpd: caught SIGSEGV, attempting to 
 > > dump
 > > core in /home/karrerl/apache-bin
 
 That is bad.  If it can make Apache core dump, then Apache is broken no
 matter what the other software may be doing wrong.
 
 Do you have a core dump in the directory referenced?  If not, use the
 CoreDumpDirectory directive to change it to a directory that the user
 Apache runs as can write to, then see if you can get a core.  First
 compile your binary with '-g' in the EXTRA_CFLAGS.
 
 Do you have a debugger (gdb or dbx, etc.) on the system?  Do you know how
 to use it to see where it seems to be dying?
 

Reply via email to