Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 31171 invoked by uid 500); 12 Nov 2001 17:29:06 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 31093 invoked from network); 12 Nov 2001 17:29:06 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Ryan Bloom Reply-To: rbb@covalent.net Organization: Covalent Technologies To: dev@httpd.apache.org, Dale Ghent Subject: Re: segfault with worker, ap_lingering_close Date: Mon, 12 Nov 2001 09:21:14 -0800 X-Mailer: KMail [version 1.3] References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011112172114.B427246DFD@koj.rkbloom.net> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Monday 12 November 2001 06:15 am, Dale Ghent wrote: > On Mon, 12 Nov 2001, Cliff Woolley wrote: > | If you run the httpd-test limits.t test with the worker MPM (on Linux at > | least), you'll see that it hangs trying to perform subtest #2, though the > | test doesn't hang with prefork. It was kind of rough coaxing gdb into > | telling me what was going on (we all know how well > | linux+gdb+multithreading get along :-/ ), but anyway, here's the > | backtrace: > > yeah, I've been seeing this with httpd+worker on solaris 8. I included a > stack trace of it in my second mail to the list yesterday entitled "Two > apache/2.0.29-dev problems" My best guess is that occasionally, the socket is being cleaned before lingering close is called. I'll be modifying the order of that code today, which may solve the problem. Ryan ______________________________________________________________ Ryan Bloom rbb@apache.org Covalent Technologies rbb@covalent.net --------------------------------------------------------------