httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathihalli, Madhusudan" <mad...@hp.com>
Subject RE: SEGV in allocator_free
Date Sat, 20 Mar 2004 00:49:42 GMT
Some more data points:

the error DOES NOT happen on (vanilla) 2.0.48
- it happens on (vanilla) 2.0.49 

-Madhu

>-----Original Message-----
>From: William A. Rowe, Jr. [mailto:wrowe@rowe-clan.net]
>Sent: Friday, March 19, 2004 11:46 AM
>To: dev@httpd.apache.org
>Cc: dev@httpd.apache.org
>Subject: RE: SEGV in allocator_free
>
>
>At 01:30 PM 3/19/2004, Mathihalli, Madhusudan wrote:
>>>-----Original Message-----
>>>From: Sander Striker [mailto:striker@apache.org]
>>[SNIP]
>>>
>>>allocator = 0x0, that's bad.  You didn't do a full httpd rebuild, so
>>>there is no way of telling what pool this is.  Can you do a full
>>>rebuild (with pool debugging enabled)?  Is this vanilla httpd-2.0.48?
>>
>>Pretty much - with some minor fixes for HP-UX, and some SSL 
>fixes that've gone into the 2.0.49 release.
>>(fix mem leak and send the 'close-alert' message)
>
>so the mem leak fix is there?
>
>if the segfault reoccurs - would you validate that the vanilla 
>2.0.48 suffered
>the same segv?
>
>
>
>

Mime
View raw message