Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 7 Nov 2000 15:40:38 -0500 From: Christopher Faylor To: "'cygwin@sources.redhat.com'" Subject: Re: Error: couldn't make stderr distinct from stdout Message-ID: <20001107154038.A11743@redhat.com> Reply-To: cygwin@sources.redhat.com Mail-Followup-To: "'cygwin@sources.redhat.com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: ; from Chris.Georges@disney.com on Tue, Nov 07, 2000 at 12:23:10PM -0800 On Tue, Nov 07, 2000 at 12:23:10PM -0800, Georges, Chris wrote: >> From: Larry Hall (RFK Partners Inc) [mailto:lhall@rfk.com] >> Sent: Tuesday, November 07, 2000 10:26 AM >> To: Georges, Chris; 'cygwin@sourceware.cygnus.com' >> Subject: Re: Error: couldn't make stderr distinct from stdout >> >> >> At 01:30 AM 11/7/2000, Georges, Chris wrote: >> >>>I just upgraded my cygwin installation from 1.0 to the latest cygwin >>>DLLs (cygwin-1.1.5-4) and now almost every utililty (ls,cat,etc) prints >>>out "couldn't make stderr distinct from stdout" when it starts. tcsh >>>prints the error and exits. I backed out to cygwin-1.1.4 and got the >>>same problem. I am running all of these apps remotely in a telnet >>>window connected a windows 2000 telnet server (the default one that >>>comes with win2k) on a remote machine, this worked fine until I >>>upgraded cygwin. The apps appear to run OK when run in a normal window >>>on the local machine. >> >>A cygcheck -s -r -v may be helpful. My guess is you have a mixture of >>1.0 and 1.1.x stuff that's causing you troubles, but that's purely a >>guess. The results of cygcheck should help you determine this. > >I think the problem is in cygwin1.dll, which is printing out that >message in stdio_init() in source file "winsup\cygwin\dtable.cc". It's >calling DuplicateHandle() which apparently fails, and somehow the error >causes everything to exit. I couldnt find a corresponding function in >the source for cygwin 1.0. I backed out to the cygwin 1.0 version of >cygwin1.dll and the message went away. The *fact* that an error is being printed is not indicative of an error in cygwin1.dll. The same code is in 1.0 and 1.1.x. Larry's suggestion of running 'cygcheck -s -r -v' was the best way to debug your problem. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com