Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<3.0.5.32.20031230104540.00831340@incoming.verizon.net>
X-Sender:	vze1u1tg AT incoming DOT verizon DOT net
Date:	Tue, 30 Dec 2003 10:45:40 -0500
To:	cygwin AT cygwin DOT com
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject:	Re: Please try the latest snapshot -- it is close to cygwin 1.5.6
In-Reply-To:	<3.0.5.32.20031227182809.0082b100@incoming.verizon.net>
References:	<20031227174656 DOT GA10264 AT redhat DOT com> <3 DOT 0 DOT 5 DOT 32 DOT 20031226222751 DOT 00803100 AT incoming DOT verizon DOT net> <3 DOT 0 DOT 5 DOT 32 DOT 20031226211336 DOT 00804140 AT incoming DOT verizon DOT net> <20031226204641 DOT GA46362839 AT hpn5170x> <20031224152951 DOT GA34487383 AT hpn5170x> <20031223222816 DOT GA23935 AT redhat DOT com> <20031224152951 DOT GA34487383 AT hpn5170x> <3 DOT 0 DOT 5 DOT 32 DOT 20031224181524 DOT 007c21c0 AT incoming DOT verizon DOT net> <20031224232759 DOT GA12748 AT redhat DOT com> <20031226204641 DOT GA46362839 AT hpn5170x> <3 DOT 0 DOT 5 DOT 32 DOT 20031226211336 DOT 00804140 AT incoming DOT verizon DOT net> <3 DOT 0 DOT 5 DOT 32 DOT 20031226222751 DOT 00803100 AT incoming DOT verizon DOT net>
Mime-Version:	1.0

Christopher Faylor wrote:
>
>I fixed some more problems with both vfork and with fork recently.  The
>fixes are currently in cvs.

It's much better. 

CYGWIN_ME-4.90 hpn5170x 1.5.6(0.108/3/2) 2003-12-29 22:44 i686 unknown
unknown Cygwin

I only have problems with the more complicated tests.
Open two tty windows, tty0 and tty1.
In the tty0 window, type
setsid bash -c "echo hello > /dev/tty1; /bin/sleep 10; /bin/echo there >
/dev/tty"
 
Note the first echo is a built-in and the last /dev/tty (not /dev/tty1). 
Things go as I think they should: "echo" & "there" appear in the tty1 window, 
and ps shows that bash and sleep have tty1 as ctty. 

However when using sh,
setsid sh -c "echo hello > /dev/tty1; /bin/sleep 10; /bin/echo there >
/dev/tty"
sh and the final echo hang forever (with echo in the "O" state in ps),
and sh cannot be terminated with kill (OK from the task manager).
Moreover sysinternals shows that tty1 is not opened in sh, nor in /bin/echo
(despite
being the ctty), although it is open in /bin/sleep.
(My sandbox is slightly different from cvs, but "it shouldn't matter").
 
Also I still observe processes terminating with the "error in Cygwin1.dll"
popup 
(exim, mutt, tty, id, dircolors). JIT gdb kicked in once. Only thread 1 was
active 
and I couldn't get any useful info. I didn't see the "proc lock"
system_printf.

Pierre


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

- Raw text -