Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 97927 invoked from network); 20 Sep 2009 00:56:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Sep 2009 00:56:01 -0000 Received: (qmail 58567 invoked by uid 500); 20 Sep 2009 00:56:01 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 58466 invoked by uid 500); 20 Sep 2009 00:56:00 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 58458 invoked by uid 99); 20 Sep 2009 00:56:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2009 00:56:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bojan@rexursive.com designates 150.101.121.179 as permitted sender) Received: from [150.101.121.179] (HELO beauty.rexursive.com) (150.101.121.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2009 00:55:51 +0000 Received: from [10.1.120.24] (shrek.rexursive.com [10.1.120.24]) by beauty.rexursive.com (Postfix) with ESMTP id 8FEA08C9E1; Sun, 20 Sep 2009 10:55:28 +1000 (EST) Subject: Re: Crash in apr_file_close() (Win32) From: Bojan Smojver To: "Yuri V. Vishnevskiy" Cc: dev@apr.apache.org In-Reply-To: References: Content-Type: text/plain Date: Sun, 20 Sep 2009 10:55:28 +1000 Message-Id: <1253408128.2511.19.camel@shrek.rexursive.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Sat, 2009-09-19 at 23:34 +0700, Yuri V. Vishnevskiy wrote: > I have a problem with using stdout stream opened by > apr_file_open_stdout() > function. If I open several stdout handlers in my program then it > crashes > when calls apr_file_close() function more than one time. Could you run it within a debugger and then give us a stack trace? -- Bojan