From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10005300025.AA14354@clio.rice.edu>
Subject:	Re: W2k
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date:	Mon, 29 May 2000 19:25:49 -0500 (CDT)
Cc:	djgpp-workers AT delorie DOT com
In-Reply-To:	<Pine.SUN.3.91.1000529104108.24119K-100000@is> from "Eli Zaretskii" at May 29, 2000 10:42:39 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> > So, maybe the unhooking helps if it is done at the top level?
> 
> Well, to test this hypothesis, how about running the full libc build
> under redir?  Library build is very deeply nested (I think it gets up
> to 4 or 5 levels of nested invocations), and runs lots of programs, so
> it should be a good test.

No this wouldn't help (just adding redir at the top doesn't fix 3 nestings
below it if they all hook).  It looks like we would need a flag to 
suppress the hooking (both FPU and Keyboard? just one or the other?) in 
something like make (?) which is at the top level and nests alot.

The question is - does this get fixed in some service pack?  I haven't
installed SP1 yet.

- Raw text -