Greg Ames wrote:
> Program received signal SIGSEGV, Segmentation fault.
> apr_pool_clear (a=0x0) at apr_pools.c:869
> 869 while (a->sub_pools) {
> (gdb) bt
> #0 apr_pool_clear (a=0x0) at apr_pools.c:869
> #1 0x08090320 in apr_pool_destroy (a=0x0) at apr_pools.c:920
> #2 0x4027d2ff in cgid_maint (reason=0, data=0x811a724, status=15)
> at mod_cgid.c:238
> #3 0x0808dd69 in apr_proc_other_child_check () at otherchild.c:208
> #4 0x0806ccfc in ap_reclaim_child_processes (terminate=1) at
> mpm_common.c:175
> #5 0x08064553 in ap_mpm_run (_pconf=0x80c443c, plog=0x80e453c,
> s=0x80c4984)
> at threaded.c:1329
> #6 0x08068e50 in main (argc=1, argv=0xbffff734) at main.c:427
> #7 0x4013f0de in __libc_start_main () from /lib/libc.so.6
>
> I've taken mod_cgid out of my build for now (didn't realize I had it
> actually) and see what happens.
OK, graceless restarts are working again in threaded with mod_cgid out
of the picture.
Greg
- Re: Currently known issues with 2.0.23 (ver... Cliff Woolley
- Re: Currently known issues with 2.0.23 ... Jerry Baker
- Re: Currently known issues with 2.... Doug MacEachern
- Re: Currently known issues wit... Jerry Baker
- Re: Currently known issues wit... Doug MacEachern
- Re: Currently known issues with 2.0.23 (very few! :... Ryan Bloom
- Re: Currently known issues with 2.0.23 Cliff Woolley
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Jeff Trawick
- Re: Currently known issues with 2.0.23 Jeff Trawick
- Re: Currently known issues with 2.0.23 Greg Ames
- Re: Currently known issues with 2.0.23 Jeff Trawick
- Re: Currently known issues with 2.0.23 (very few! :) Justin Erenkrantz
- Re: Currently known issues with 2.0.23 (very few! :) Ryan Bloom
- Re: Currently known issues with 2.0.23 Cliff Woolley
- Re: Currently known issues with 2.0.23 Ryan Bloom
- Re: Currently known issues with 2.0.23 Ian Holsman
