From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-28362-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 12384 invoked by alias); 13 Apr 2007 11:47:39 -0000
Received: (qmail 12370 invoked by uid 22791); 13 Apr 2007 11:47:39 -0000
X-Spam-Check-By: sourceware.org
Received: from province.act-europe.fr (HELO province.act-europe.fr) (212.157.227.214)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 13 Apr 2007 12:47:35 +0100
Received: by province.act-europe.fr (Postfix, from userid 560) 	id A8172164E48; Fri, 13 Apr 2007 13:47:32 +0200 (CEST)
Date: Fri, 13 Apr 2007 11:47:00 -0000
From: Jerome Guitton <guitton@adacore.com>
To: Dave Korn <dave.korn@artimi.com>
Cc: 'Joel Brobecker' <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: [mingw32] stdin redirection
Message-ID: <20070413114732.GA33253@adacore.com>
References: <20070411134219.GA33609@adacore.com> <20070411144451.GA21140@caradoc.them.org> <20070411145104.GE58502@adacore.com> <20070411151234.GA22185@caradoc.them.org> <20070412145818.GG3886@adacore.com> <20070412151221.GA856@caradoc.them.org> <20070412164744.GL3886@adacore.com> <018d01c77d27$7610fd90$2e08a8c0@CAM.ARTIMI.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <018d01c77d27$7610fd90$2e08a8c0@CAM.ARTIMI.COM>
User-Agent: Mutt/1.4.2.1i
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-04/txt/msg00089.txt.bz2

Dave Korn (dave.korn@artimi.com):

> In some circumstances, you can also use a file, named pipe, or communications
> device as a synchronization object; however, their use for this purpose is
> discouraged. Instead, use asynchronous I/O and wait on the event object set in
> the OVERLAPPED structure. It is safer to use the event object because of the
> confusion that can occur when multiple simultaneous overlapped operations are
> performed on the same file, named pipe, or communications device. In this
> situation, there is no way to know which operation caused the object's state
> to be signaled.

So we should probably associate an event object to stdin in the file
case (just like what we do for ttys and pipes). I will allocate some
time to work on this on monday.