On Thu, Jan 07, 1999, [EMAIL PROTECTED] wrote:
> Full_Name: Ernest YIK
> Version: 2.1.6
> OS: Slackware Linux 3.6
> Submission from: venus.csc.cuhk.edu.hk (137.189.4.5)
>
> Configuration :
> Slackware Linux 3.6, Linux kernel 2.0.36.
> Apache 1.3.3, mod_ssl 2.1.6 (2.1.3 and 2.1.4 gave the same segfault)
> SSLeay-0.9.0b
>
> The apache server will segfault on certain (but not all) requests on
> port 443. error_log contains the following messages :
>
> [Thu Jan 7 15:56:04 1999] [notice] Apache/1.3.3 (Unix) mod_ssl/2.1.6
> SSLeay/0.9.0b configured -- resuming normal operations
> [Thu Jan 7 15:56:08 1999] [notice] httpd: child pid 4304 exit signal
> Segmentation fault (11)
> [Thu Jan 7 15:56:15 1999] [notice] httpd: child pid 4305 exit signal
> Segmentation fault (11)
> [Thu Jan 7 15:56:32 1999] [notice] httpd: caught SIGTERM, shutting
> down
>
> Compiled Apache with OPTIM="-g -ggdb3", make sure that the files are
> not stripped and added directive "CoreDumpDirectory /tmp" in
> httpd.conf, but still no core file anywhere when the seg fault occurs.
> Only managed to run httpd with gdb and get the output (attached below).
You have to temporarily run it as non-root on port 8443 to get the core dump
on such platforms.
> Now fall back to Apache 1.3.2 with mod_ssl 2.0.12 and everything
> are ok, no segfaults.
Hmmm... looks crazy. I've never seen such general segfaults on any 2.1.x
versions which occur for every request.
>[...]
> (gdb) run -X -DSSL
> Starting program: /usr/local/apache/sbin/httpd -X -DSSL
> Apache/1.3.3 mod_ssl/2.1.6 (Pass Phrase Dialog)
> Some of your private key files are encrypted for security reasons.
> In order to read them you have to provide us with the pass phrases.
>
> Server xxxx.yyyy.zzz:443
> Enter pass phrase:
>
> Ok: Pass Phrase Dialog successful.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x4007e9e0 in memcpy ()
> (gdb) bt
> #0 0x4007e9e0 in memcpy ()
> #1 0x0 in ?? ()
> (gdb)
Hmmm... the only memcpy()'s in mod_ssl are cache related. So, either these
are those which fail on your platform or it's a memcpy inside SSLeay. We
really need a better backtrace. So, please try to run the non-stripped httpd
(not the installed one, the one in apache_1.3.3/src/) as non-root on port 8443
and then try to get a better backtrace for me by looking at the generated core
dump again. Is this possible?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
