From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: /dev/p* causes shell crash in i686
Date: Thu, 10 Sep 2020 21:31:01 +0200 [thread overview]
Message-ID: <df188735-815e-6b0e-5af5-f535b1161fad@towo.net> (raw)
In-Reply-To: <02fccd98-5371-2399-ce86-ddd1a545f298@cornell.edu>
Am 10.09.2020 um 21:19 schrieb Ken Brown via Cygwin:
> On 9/10/2020 3:15 PM, Andrew Schulman via Cygwin wrote:
>>> On Sep 9 08:08, Andrew Schulman via Cygwin wrote:
>>>> Here's a strange one. In bash in i686, try to run:
>>>>
>>>> ls /dev/ptmx
>>>>
>>>> I only get about as far as:
>>>>
>>>> ls /dev/p
>>>>
>>>> and then my terminal window vanishes. This happens:
>>>>
>>>> * In fish or bash.
>>>> * On two different hosts that I've tried.
>>>> * In mintty or a system terminal. In the system terminal, sometimes
>>>> the
>>>> command works normally the first time, but fails the 2nd time; or I
>>>> have to
>>>> press <TAB> after `ls /dev/p`, then the terminal vanishes.
>>>> * With other commands that treat their arguments as files, not
>>>> text. So for
>>>> example, I can't finish typing `cat /dev/ptmx` or `test -r /dev/ptmx`
>>>> before the terminal window vanishes, but `echo /dev/ptmx` works
>>>> normally.
>>>>
>>>> It doesn't happen:
>>>>
>>>> * In x86_64 - only i686.
>>>> * In scripts - only interactively.
>>>>
>>>> Is anyone else able to reproduce this? I've tried to capture an
>>>> strace log,
>>>> but I've failed so far. The strace seems to stop the crash. Still
>>>> trying.
>>>>
>>>> I thought this could be a BLODA problem, but the two hosts I tried are
>>>> running different virus scanners (McAfee and Windows Defender).
>>>>
>>>> Cygwin 3.1.7-1, all packages up-to-date. Output of cygcheck -svr
>>>> attached.
>>>>
>>>> Andrew
>>>
>>> I think I fixed it. I just uploaded new developer snapshots to
>>> https://cygwin.com/snapshots/ Please give them a try.
>>
>> When I substitute cygwin1-20090909.dll for cygwin1.dll in i686, I
>> can't run
>> any commands. They all give "The application was unable to start
>> correctly
>> (0xc0000022)". Anything different I should be doing?
>
> Check the permissions on cygwin1-20090909.dll. Is it executable?
cygwin1-20090909.dll is 11 years old. Did you download the latest snapshot?
next prev parent reply other threads:[~2020-09-10 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:08 Andrew Schulman
2020-09-09 14:54 ` Eliot Moss
2020-09-09 21:49 ` Corinna Vinschen
2020-09-10 19:15 ` Andrew Schulman
2020-09-10 19:19 ` Ken Brown
2020-09-10 19:31 ` Thomas Wolff [this message]
2020-09-10 19:38 ` Ken Brown
2020-09-10 19:41 ` Thomas Wolff
2020-09-10 19:44 ` Brian Inglis
2020-09-10 19:38 ` Brian Inglis
2020-09-10 22:37 ` Andrew Schulman
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=df188735-815e-6b0e-5af5-f535b1161fad@towo.net \
--to=towo@towo.net \
--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).