This is the mail archive of the
mailing list for the Cygwin project.
Re: problems with the latest snapshot
- To: Earnie Boyd <email@example.com>
- Subject: Re: problems with the latest snapshot
- From: Chris Faylor <firstname.lastname@example.org>
- Date: Fri, 30 Jul 1999 10:07:23 -0400
- Cc: cygwin developers <email@example.com>
- References: <firstname.lastname@example.org>
On Fri, Jul 30, 1999 at 05:34:10AM -0700, Earnie Boyd wrote:
>> > it seems that there're some problems with signal handling in the
>> >latest snapshots the first one is that bash freezes at startup if it's
>> >being started from sh. It seems that this error prevents sshd from
>> >running user shell.
>> I think that this is really an ASH bug. I have been playing with a
>> new version of ASH for some time. If anyone wants to try it, go to
>> and retrieve
>> sh.exe.bz2 # the executable
>> ash.tar.bz2 # the source
>Actually, I saw this behaviour a couple of nights ago when I was working with
>Corinna on her security patch. By the way, I think she has that problem
>resolved. I sent her a strace of this bash freezing when started from sh
>problem. It doesn't just freeze, it goes into an endless loop which is really
>noticable in the strace file. This endless loop is IMO not a problem with ash
>but a runtime problem.
The bash hanging behavior that Egor Duda reported is easy to reproduce
and I know exactly why it happened. I can trace it back to some early
snapshots where it only occurred if you set CYGWIN=tty. As I have been
consolidating the functionality of ttys and console devices, I ended up
"breaking" this behavior under normal console I/O, too. It is
definitely an ash problem. You'll notice the same behavior if you port
ash to linux and run bash under it.
This is probably unrelated to the problems that you were experiencing.