From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: cygwin1.dll (file version 1003.6.0.0) dup problem with gcc
Date: Tue, 08 Jan 2002 07:49:00 -0000 [thread overview]
Message-ID: <20020108155006.GB22944@redhat.com> (raw)
In-Reply-To: <718198F862F1D411B10F0002A50A4DB101A4F0FA@e90wwce3.dx.deere.com>
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/
next prev parent reply other threads:[~2002-01-08 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 7:26 Polley Christopher W
2002-01-08 7:49 ` Christopher Faylor [this message]
[not found] <718198F862F1D411B10F0002A50A4DB101A4F0E8@e90wwce3.dx.deere .com>
2001-12-18 16:29 ` Larry Hall (RFK Partners, Inc)
-- strict thread matches above, loose matches on Subject: below --
2001-12-17 12:19 Polley Christopher W
2001-12-17 11:39 Polley Christopher W
2001-12-17 10:54 Suman Kumar Ray
2001-12-17 11:25 ` Larry Hall (RFK Partners, Inc)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020108155006.GB22944@redhat.com \
--to=cgf@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).