Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 59967 invoked by uid 500); 6 May 2003 15:09:45 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 59879 invoked from network); 6 May 2003 15:09:44 -0000 Received: from sunstarsys.com (HELO w2.sunstarsys.com) (64.227.73.173) by daedalus.apache.org with SMTP; 6 May 2003 15:09:44 -0000 Received: from sol.sunstarsys.com (mumonkan.sunstarsys.com [67.34.76.193]) by w2.sunstarsys.com (8.11.6/8.11.0) with ESMTP id h46F9f106517; Tue, 6 May 2003 11:09:42 -0400 Received: (from joe@localhost) by sol.sunstarsys.com (8.12.8/8.12.8/Submit) id h46FB7AS031944; Tue, 6 May 2003 11:11:07 -0400 To: Arthur Bergman , apreq-dev@httpd.apache.org Subject: Re: Perl segfault in 5.8 References: <3EB78380.5040504@stason.org> From: Joe Schaefer Date: 06 May 2003 11:11:06 -0400 In-Reply-To: <3EB78380.5040504@stason.org> Message-ID: Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stas Bekman writes: > [redirecting to the right mailing list] > > Arthur Bergman wrote: > > Hi, > > We are having a problem with weird segfaults in IO_flush. > > Reading old emails I see this > > http://mathforum.org/epigone/modperl/zhoolamgheld/ > > Pine.LNX.4.33.0206131508310.955-100000@mako.covalent.net > > but this does not seem to be applied to libapreq, any reason why? > > Arthur ISTR a pair of discussions, this being the first of the two. I don't know why Doug didn't apply this patch, but I did apply his other one. Looking at the Request.xs code, it seems that we're duping the tempfile's underlying file descriptor before handing it off to PerlIO. We should flush the stdio buffers *before* doing that, but currently I don't think we are. OTOH, I'd expect a potential data-corruption problem here, not a segfault. Have you got a test case or backtrace for us to look at? -- Joe Schaefer