DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=mjk20Ej46o19PEzZv5MLdo819ZMYq5Wnw1u+CAkSUlM
	MhSh89x6iDFR0hM+m7YnyRfy6JgrlKsR11un9sjGAyo0rSx/HS1oVM7M05jKjPRW
	rxidtfbWMPLUC0mpRS2hflq4ZMgPhrkiTIgJhnuUx0BCd3PHfEF25zal5d0TSYbA
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 6 Nov 2019 20:58:12 +0900
From: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin 3.1.x fails if I have the use legacy console box   checked in Windows 10
Message-Id: <20191106205812.89ba47e9a819d52ae7941279@nifty.ne.jp>
In-Reply-To: <20191105192430.E05A5440070@conbox-039.nifty.com>
References: <20191105192430 DOT E05A5440070 AT conbox-039 DOT nifty DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Michael,

Thanks for the report.

On Tue, 05 Nov 2019 14:24:06 -0500
"Michael D. Lawler" wrote:
> It looks like the changes between 3/27 and 3/31 were to support 
> 24-bit color in the normal console in 1703 or later and to fake the 
> support for legacy console.  I can't currently compile anything, but 
> I'm guessing that something went wrong with that change for legacy 
> console.  The other changes seem less likely to cause the problem 
> based on reading the diff.
> 
> At 10:34 PM 11/4/2019, you wrote:
> >I'm using Win 10 1903 build 18362.449 and if I check the use legacy 
> >console box under properties options in the console then I get the 
> >following error with ssh built with cygwin.
> >       0 [main] ssh 1942 C:\Program Files\OpenSSH\bin\ssh.exe: *** 
> > fatal error - couldn't initialize fd 0 for /dev/cons0
> >    5898 [main] ssh 1942 cygwin_exception::open_stackdumpfile: 
> > Dumping stack trace to ssh.exe.stackdump
> >
> >
> >Stack trace:
> >Frame        Function    Args
> >00000010000  00180060B7E (00180267ED8, 0018025A1B9, 000FFFFFFFF, 000FFFFBA50)
> >00000010000  00180049249 (0018006CEBF, FFFFFFFFFFFFFFFF, 
> >00000000000, 000FFFFCB00)
> >00000010000  00180049282 (00000000000, 0018035FC20, 000FFFFFFFF, 000FFFFCB30)
> >00000010000  0018005ABFC (000FFFFCC70, 00000000000, 001800D1BA2, 000FFFFCC70)
> >00180342D08  0018005AD46 (00100464280, 00180221860, 
> >FEFF552BFF677272, 00000000000)
> >000FFFFCCD0  00180049A0C (00000000000, 00000000000, 00000000000, 00000000000)
> >00000000000  00180048353 (00000000000, 00000000000, 00000000000, 00000000000)
> >000FFFFFFF0  00180048404 (00000000000, 00000000000, 00000000000, 00000000000)
> >End of stack trace
> >
> >
> >If I use 3.07 this works.  Also if I use the March 27 2019 snapshot 
> >it works, but if I use the March 31 2019 or later snapshot I get the 
> >above error.  I couldn't find anything that said that Cygwin now 
> >didn't support the legacy console thus I'm reporting this issue.

I will submit a patch to fix this issue soon.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple