>Number: 3503 >Category: mod_proxy >Synopsis: SIGSEGV >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Dec 7 09:30:00 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.3 >Environment: gcc, Solaris 2.5.1, apache 1.3.3 >Description: Mhh, I've noticed some problems after upgrading to 1.3.3.
Log-File (error_log): --------------------- [Mon Dec 7 17:06:30 1998] [notice] httpd: child pid 10943 exit signal Segmentat ion Fault (11), possible coredump in /tmp [Mon Dec 7 17:10:00 1998] [notice] httpd: child pid 10206 exit signal Segmentat ion Fault (11), possible coredump in /tmp [ -------- BackTrace ------ gdb: #0 0x23ac8 in ap_proxy_send_fb () (gdb) (gdb) bt #0 0x23ac8 in ap_proxy_send_fb () #1 0x22154 in ap_proxy_http_handler () #2 0x171e4 in ap_get_server_built () #3 0x4b4a0 in ap_invoke_handler () #4 0x65bc0 in ap_some_auth_required () #5 0x65c40 in ap_process_request () #6 0x5ab54 in ap_child_terminate () #7 0x5aea8 in ap_child_terminate () #8 0x5b3c8 in ap_child_terminate () #9 0x5bb40 in ap_child_terminate () #10 0x5c394 in main () I've tried the URLs in the accesslog nearby to the time the coredump occurred - but I couldn't re-produce a SIGSEGV. But the log shows about 20 to 60 cores reports in the errorlog per day. Regards Rainer >How-To-Repeat: unknown... >Fix: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
