On 21 February 2014 02:23, Joe Orton <jor...@redhat.com> wrote: > On Thu, Feb 20, 2014 at 07:52:34AM -0500, Jeff Trawick wrote: > > WSGI 3.4 daemon mode crashing with httpd 2.4.x... > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0xaef17b70 (LWP 32761)] > > 0x08078a32 in update_child_status_internal () > > (gdb) where > > #0 0x08078a32 in update_child_status_internal () > > #1 0x0809952d in ap_start_lingering_close () > > #2 0x080995a9 in ap_lingering_close () > > Fixed in: > > > http://code.google.com/p/modwsgi/source/detail?path=/mod_wsgi.c&name=mod_wsgi-3.X&r=bdbeacb88f348909845445e9d52eb7be401abaf1 > > mod_wsgi does some surprising things with httpd interfaces which should > probably be internal-only, or at least better documented API! >
Crap. I thought those httpd 2.4 fixes were already in mod_wsgi 3.4. Another reason I have to get off my backside and release an updated version. Has been too long. And yes mod_wsgi does lots of evil things which no doubt would be regarded as evil. Most come from daemon mode. One day I will simply rewrite daemon mode request handling to not be dependent on Apache request structures and then it will not be so bad. Graham
