This is the mail archive of the
mailing list for the Cygwin project.
Re: tty initialization failure under cygwin 1.7.2?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 2 Apr 2010 13:36:41 +0200
- Subject: Re: tty initialization failure under cygwin 1.7.2?
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Apr 1 14:31, Eric Berge wrote:
> I recently updated to 1.7.2 from 1.7.1 with the March 15 development
> patch and noticed I was getting some process failures. In particular
> I was running the Coverity static analysis tool, and was getting an
> error about not being able to "initialize fd 0 for /dev/tty0".
> This problem does not appear to occur with remote desktop, just with
> I've been searching around for a simpler version of the problem
> and this is what I found:
> The test scenario is to do the following:
> 1. ssh into an cygwin sshd server with an explicit password
> 2. Run "cmd"
> 3. From "cmd" run "ls"
> I unfortunately no longer have the 1.7.1 + Mar15 patch running but
> with cygwin 1.5 and running "ls" lists the entries of the directory
> as expected. However, running on 1.7.2 has the following output:
> 12 [main] ls 3984 C:\cygwin\bin\ls.exe: *** fatal error - couldn't initialize fd 0 for /dev/tty0
> I hope this is reflective of the problem I had with Coverity. It is
> the same error message at least. Is this indicative of an underlying
> problem in 1.7.2 or is this related to any sort of reconfiguration I
> need to do on my box after updating to 1.7.2?
I'm wondering if that's a side effect with some other software. I can
not reproduce your problem. I tried your test scenario and it works for
me. I don't get any weird error from ls.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple