On Sat, 2004-03-20 at 02:47, Mathihalli, Madhusudan wrote: > >-----Original Message----- > >From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED] > > > >At 01:30 PM 3/19/2004, Mathihalli, Madhusudan wrote: > >>>-----Original Message----- > >>>From: Sander Striker [mailto:[EMAIL PROTECTED] > >>[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? > > > Here's the stack trace of the SEGV with 2.0.49: > > Frame 14 is apr_pool_clear and so is Frame 1 ! Is there some sort of a recursion > happening ?
This is perfectly normal. A pool is being cleared, as a result its child pools are destroyed. Sander
