Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 7 Jun 2002 11:05:49 +0200
From: Pavel Tsekov <ptsekov@syntrex.com>
Reply-To: Pavel Tsekov <cygwin@cygwin.com>
Organization: Syntrex, Inc.
Message-ID: <193840612.20020607110549@syntrex.com>
To: cygwin@cygwin.com
Subject: Re[2]: 1.3.11(CVS): Possible bug involving temp file generation
In-Reply-To: <13925672855.20020606182237@s<20020606234917.GC11320@redhat.com>
References: <20020605132012.8086.qmail@web21002.mail.yahoo.com>
 <12220356170.20020605154358@syntrex.com> <20020605150849.GF15167@redhat.com>
 <17118445663.20020606162210@syntrex.com>
 <20020606165907.F22789@cygbert.vinschen.de> <13925672855.20020606182237@s
 <20020606234917.GC11320@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello Christopher,

Friday, June 07, 2002, 1:49:17 AM, you wrote:

CF> I should reiterate that this code is *only* called when a cygwin process
CF> is invoked from a non-cygwin process with stdin/stdout/stderr redirected
CF> to a disk file.

CF> It has nothing to do with temp file creation or normal file creation.

I am aware of this fact - explaining me once is sufficient (in most
cases) :)

The original post introduced some confusion. While explaining how
to reproduce the problem with the temp file, another bug was
introduced - the STATUS_ACCESS_VIOLATION in patch (from the
strace.log). I was trying to catch this one.

Check http://cygwin.com/ml/cygwin/2002-06/msg00278.html - at the
bottom lines.

And clearly this post of mine,
http://cygwin.com/ml/cygwin/2002-06/msg00210.html, is *WRONG*. I assume
your changes in v 1.92 of dtable.cc fixed the 'Bad file
number' problem.

It's cool that now both of the problems are fixed! :)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/