From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-62117-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 2051 invoked by alias); 14 Mar 2009 10:45:59 -0000
Received: (qmail 2042 invoked by uid 22791); 14 Mar 2009 10:45:59 -0000
X-SWARE-Spam-Status: No, hits=3.0 required=5.0 	tests=AWL,BAYES_00,BOTNET,RCVD_IN_JMF_BL,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 14 Mar 2009 10:45:50 +0000
Received: from conversion-daemon.i-mtaout1.012.net.il by i-mtaout1.012.net.il (HyperSendmail v2007.08) id <0KGH00E00SD4I400@i-mtaout1.012.net.il> for gdb-patches@sourceware.org; Sat, 14 Mar 2009 12:45:55 +0200 (IST)
Received: from HOME-C4E4A596F7 ([77.127.228.91]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KGH00AGDSKHT240@i-mtaout1.012.net.il>; Sat, 14 Mar 2009 12:45:55 +0200 (IST)
Date: Sat, 14 Mar 2009 12:32:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch] testsuite: Fix a racy FAIL on gdb.base/multi-forks.exp
In-reply-to: <20090313161423.GF8368@adacore.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <uzlfoqt6z.fsf@gnu.org>
References: <20090313152723.GA13673@host0.dyn.jankratochvil.net> <20090313161423.GF8368@adacore.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2009-03/txt/msg00227.txt.bz2

> Date: Fri, 13 Mar 2009 09:14:23 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > Instead of the output suppression by `close (1)' some sleep would also fix it
> > if close (1) is not compatible enough.
> 
> As far as I can tell, "close" is POSIX, so should be fairly portable.
> I'm not entirely sure about Windows, but I do think it's available.
> The symbol name might be _close, though.

Windows has both _close and close.

What happens after you close(1) in a Windows console application is
anybody's guess, though.  I didn't try that.