On Fri, 2004-03-19 at 20:01, Mathihalli, Madhusudan wrote:
[...]
> >Can you give a backtrace of where it does abort? And maybe the name
> >of the pool that is being checked (p pool->tag)? Have you stepped
> >through the code with gdb?
>
> Sure.. here it is. There are 2 traces -
>
> Let me know if you need more info.
[...]
> #5 0x9fffffffef627140:0 in apr_palloc (pool=0x600000000001dc60, size=40)
> at apr_pools.c:2207
> 2207 return apr_palloc_debug(pool, size, "undefined");
> (gdb) p *pool
> $1 = {parent = 0x600000000001a420, child = 0x60000000000e59d0,
> sibling = 0x600000000001d4e0, ref = 0x600000000001a428, cleanups = 0x0,
> allocator = 0x0, subprocesses = 0x0, abort_fn = 0, user_data = 0x0,
> tag = 0x9fffffffef5e2b90 "undefined", nodes = 0x60000000000be1b0,
> file_line = 0x9fffffffef5e2b90 "undefined", creation_flags = 0,
> stat_alloc = 5, stat_total_alloc = 5, stat_clear = 0, owner = 1,
> mutex = 0x600000000001e0e0}
> (gdb)
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?
Sander
