Hi Dave. Can you try a current snapshot of the code? Available from http://dev.apache.org/from-cvs/
Is your traceback really that mangled? It's dumping immediately upon hitting proxy_http_handler(), or soon thereafter? Thanks. > > >Number: 629 > >Category: mod_proxy > >Synopsis: Apache as proxy dumps core on proxied request > >Confidential: no > >Severity: critical > >Priority: medium > >Responsible: apache (Apache HTTP Project) > >State: open > >Class: sw-bug > >Submitter-Id: apache > >Arrival-Date: Wed May 28 13:20:01 1997 > >Originator: [EMAIL PROTECTED] > >Organization: > apache > >Release: 1.2b10 > >Environment: > SunOS 4.1.3_U1 > version-id of "/usr/lang/SC2.0.1patch/acomp": SC2.0.1 10/7/93 > Sun_C_2.0.1_patch_100966-04 > >Description: > SIGSEGV traceback: > kill(0, 0x6, 0x488001, 0x8000000, 0xf08bd000, 0xef7e79b8) at 0xef7a0fc0 > abort(0, 0x9cd88, 0x80ac0, 0x95980, 0, 0xfd00a800) at 0xef7b8c84 > seg_fault(), line 1261 in "http_main.c" > _sigtramp(0, 0, 0x6, 0xefffd1f4, 0xffffdf74, 0xffffdf70) at 0xef76dc4c > proxy_http_handler(r > >How-To-Repeat: > I would think that any proxy access of 1.2b10 would tickle the bug. > >Fix: > I thought I could conditional out the loop and resume using the 1.2b7 code at > that > point, which comprises this line from the 1.2b10 loop: > i > >Audit-Trail: > >Unformatted: > > > -- chuck Chuck Murcko The Topsail Group West Chester PA USA [EMAIL PROTECTED]
