From: "Michael D. Lawler" <mdlawler@lawlers.us>
To: cygwin@cygwin.com
Subject: Re: Cygwin 3.1.x fails if I have the use legacy console box checked in Windows 10
Date: Tue, 05 Nov 2019 19:24:00 -0000 [thread overview]
Message-ID: <20191105192400.lNg6hK7ovIrHR9QxxD6bnovQCJEUrxQYlDboeDkikUw@z> (raw)
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.
>
>--
>Michael D. Lawler
>email mailto:mdlawler@lawlers.us
>
>
>--
>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
--
Michael D. Lawler
email mailto:mdlawler@lawlers.us
--
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
next reply other threads:[~2019-11-05 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 19:24 Michael D. Lawler [this message]
[not found] <20191105192430.E05A5440070@conbox-039.nifty.com>
2019-11-06 11:58 ` Takashi Yano
-- strict thread matches above, loose matches on Subject: below --
2019-11-05 3:34 Michael D. Lawler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191105192400.lNg6hK7ovIrHR9QxxD6bnovQCJEUrxQYlDboeDkikUw@z \
--to=mdlawler@lawlers.us \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).