Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 8 Jan 2002 10:50:06 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin1.dll (file version 1003.6.0.0) dup problem with gcc Message-ID: <20020108155006.GB22944@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <718198F862F1D411B10F0002A50A4DB101A4F0FA AT e90wwce3 DOT dx DOT deere DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <718198F862F1D411B10F0002A50A4DB101A4F0FA@e90wwce3.dx.deere.com> User-Agent: Mutt/1.3.23.1i On Tue, Jan 08, 2002 at 09:26:00AM -0600, Polley Christopher W wrote: >I think I've found the cause of this. > >I'll summarize the problem, since this is an old thread: >when a Windows GUI IDE calls gcc or make, the process reports >"fhandler_base::dup: dup(unknown disk file) failed, handle 0, Win32 error 6" >and crashes. > >The problem seems to occur when the [non-cygwin] application calls the >windows CreateProcess API function with one or more of the >STARTUPINFO.hStdInput, .hStdOutput, or .hStdError handles set to NULL; and >STARTF_USESTDHANDLES is set in StartupInfo.dwFlags. This should be fixed in current snapshots. cgf -- 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/