X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Mon, 4 Mar 2002 17:52:20 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: DJGPP developers <djgpp-workers AT delorie DOT com>
Subject: Re: New Win2K/XP bug report
In-Reply-To: <10203041542.AA17655@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1020304175022.11860A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 4 Mar 2002, Charles Sandmann wrote:

> > If so, we could change system.c and/or dosexec.c to do that on W2K.
> > (That might lose long command lines, but losing the whole pipe is much 
> > worse, I think ;-)
> 
> The problem only appears to happen if you are sending the output from
> a Win32 executable to a DJGPP executable stdin.  DJGPP to DJGPP or Win32 
> to console or Win32 to Win32 all seem to work OK.
> 
> That's a pretty ugly test.

Not really: dosexec.c already has a test for PE executables, so it 
already knows what kind of program is it about to run.  All we need is to 
run PE programs on W2K via the system shell.

This will also catch some of the cases where we could invoke the program 
directly, but so what?