Return-Path: Delivered-To: apmail-apache-bugdb-archive@apache.org Received: (qmail 33890 invoked by uid 500); 15 Oct 2000 05:50:01 -0000 Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm Precedence: bulk Reply-To: apache-bugdb@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-bugdb@apache.org Received: (qmail 33871 invoked by uid 501); 15 Oct 2000 05:50:01 -0000 Date: 15 Oct 2000 05:50:01 -0000 Message-ID: <20001015055001.33870.qmail@locus.apache.org> To: apache-bugdb@apache.org Cc: apache-bugdb@apache.org, From: Michael Long Subject: RE: os-osf/6680: segmentation fault (11) - client-induced crashes Reply-To: Michael Long The following reply was made to PR os-osf/6680; it has been noted by GNATS. From: Michael Long To: William A Rowe Jr Cc: apbugs@apache.org Subject: RE: os-osf/6680: segmentation fault (11) - client-induced crashes Date: Sun, 15 Oct 2000 01:43:40 -0400 Yeah just to let you know I am getting ready to submit a patch with about 10 bug fixes/improvements for 1.3.14 dealing with Tru64/OSF but I had this one last 1.3.x bug I couldn't figure out. I'd like to duplicate those to 2.0 as well to make sure Tru64 support is up to speed, but I couldn't get it to compile. So that's why I am submitting both 1.3.x and 2.0 bugs :) --On Sunday, October 15, 2000 12:23 AM -0500 William A Rowe Jr wrote: > In 2.0!?! this was a 1.3.x report? Retry under 1.3.14 for certain, > and append to the original report. I'm sorry, had just read your > bug report on 2.0a7/osf compile fails :-( > > If it's a tru/64 bug - I'll bet dollars to donuts that we made a bad > assumption on the size of the int type that blew up into this segfault. > > Bill > >> -----Original Message----- >> From: Michael Long [mailto:mlong@infoave.net] >> Sent: Sunday, October 15, 2000 12:16 AM >> To: William A Rowe Jr >> Subject: RE: os-osf/6680: segmentation fault (11) - client-induced >> crashes >> >> >> You mean SSI in 1.3.12 is unstable or in 2.0alpha? >> >> Could you tell if this was indeed caused by the ../ in the URL? >> >> --On Saturday, October 14, 2000 11:54 PM -0500 William A Rowe Jr >> wrote: >> >> > As soon as I noticed this ... >> > >> >> 1 handle_include(in = 0x14142cb10, r = 0x1400f3360, error >> >> = 0x11fff7c70 = "[a >> >> n error occurred while processing this directive]", noexec = >> >> 0) ["mod_include.c" >> >> :715, 0x120154004] >> > >> > I realized where you were. SSI is not presently stable, in fact >> > rbb and a few others are working on a complete overhaul. Since >> > Apache 2.0 is based on filtering, SSI is one of the key targets >> > to benefit (it is a filter in it's own right, not really the >> > usual 'handler'.) It's already undergone pretty massive changes >> > and I don't expect the 2.0a8 version will look anything like this >> > version (as you note, it's rather buggy at this moment.) >> > >> > I'll leave this note open until the overhaul is complete. Thanks >> > for your report, and interest in the Apache Alpha-2.0 project! >> > >> >> >> >> >> Michael Long >> Senior Systems Analyst >> Info Avenue Internet Services, LLC >> Michael Long Senior Systems Analyst Info Avenue Internet Services, LLC