Re: [apache-ssl] Segfaults after large CGI outputs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [apache-ssl] Segfaults after large CGI outputs




    Try upgrading to SSLeay 0.9.0b. I was experiencing Seg Faults with
Netscape and not IE; I was using SSLeay 0.8.0 -- When I upgraded, the Seg
Faults went away.

    -Jeff
--
Jeffrey Mahoney
System Programmer
Information Systems and Computing
Rochester Institute of Technology
Rochester NY
Ph: 716-475-2258
-----Original Message-----
From: Richard Gould <richard@multithread.co.uk>
To: apache-ssl@lists.aldigital.co.uk <apache-ssl@lists.aldigital.co.uk>
Date: Friday, August 14, 1998 6:31 AM
Subject: Re: [apache-ssl] Segfaults after large CGI outputs


>Mark Shuttleworth wrote:
>>
>> Hi all
>>
>> Running 1.20 (Thanks, Ben ;-) and the only glitch seems to be that
>> httpsd segfaults whenever a CGI script dumps a large page (I see it on
>> pages >200k, I don't know what the cutoff is).
>>
>> Otherwise, this one seems fairly stable and happy.
>>
>> Any ideas?
>
>Something similar happens to me but without running a script - it seems
>to happen when you load bigger files.  In my case a 28K html file causes
>a segfault, a 12K html file doesn't.
>
>Build Details:
>Red Hat 5.0 - 2.0.31
>Apache 1.3.1 + SSLeay 0.80 + SSL 1.20
>gcache not compiled-in
>
>Log message
>notice httpd: child pid 1098 exit signal: Segmentation fault (11)
>
>Ben - if you need more info give me some clues as to what to do and I'll
>do the necessary gathering.
>--
>Richard Gould
>
>MultiThread Consultants Ltd
>http://www.multithread.co.uk
>email: richard@multithread.co.uk
>