/dev/p* causes shell crash in i686

Andrew Schulman schulman.andrew@epa.gov
Thu Sep 10 19:15:48 GMT 2020


> 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?



More information about the Cygwin mailing list