one more trace: (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb7d43bbb in pthread_setspecific () from /lib/libpthread.so.0 #2 0x080c92de in child_main (child_num_arg=0) at worker.c:1258 #3 0x080c9434 in make_child (s=0x8109270, slot=0) at worker.c:1341 #4 0x080c9cbc in ap_mpm_run (_pconf=0x81020a8, plog=0x814c1d0, s=0x8109270) at worker.c:1543 #5 0x080686b8 in main (argc=6, argv=0xbfafb7d4) at main.c:717
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 3:36 PM To: dev@httpd.apache.org Subject: RE: module crashing after upgrade to 2.6 kernel and glibc 2.3.4 here is backtrace: (gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb7d43bbb in pthread_setspecific () from /lib/libpthread.so.0 #2 0x080c92de in ap_graceful_stop_signalled () #3 0x080c9434 in ap_graceful_stop_signalled () #4 0x080c9cbc in ap_mpm_run () #5 0x080686b8 in main () -----Original Message----- From: William A. Rowe, Jr. [ mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: Friday, February 23, 2007 10:50 PM To: dev@httpd.apache.org Subject: Re: module crashing after upgrade to 2.6 kernel and glibc 2.3.4 [EMAIL PROTECTED] wrote: > Hi, > I hv recently upgraded kernel of my box to linux 2.6 and also > glibc to 2.3.4. One of my custom apache 2.2 modules which was working > earlier fine is crashing now. > > Anybody faced similar problem? Present a backtrace? Try turning EnableMMAP/EnableSendfile off? Also perhaps something with the acceptfilter, try AcceptFilter (proto) off, e.g. AcceptFilter http none? The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it. The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
