X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 26 May 2010 13:50:26 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: vfork always fail problem
Message-ID:	<20100526115026.GH10652@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<AANLkTikoAoUAarNLwuIHe6GypKg62rjKR1VPyQYygT17 AT mail DOT gmail DOT com> <20100514192202 DOT GB8785 AT calimero DOT vinschen DOT de> <u1vd9ahgy DOT fsf AT acm DOT org> <20100518143136 DOT GB5909 AT ednor DOT casa DOT cgf DOT cx> <4BF2A806 DOT 9030603 AT redhat DOT com> <20100518150957 DOT GA7838 AT ednor DOT casa DOT cgf DOT cx> <AANLkTin7KqzhnMG0Zdc0hP6YRUjJGhGLwfwF8K8vOOgt AT mail DOT gmail DOT com> <op DOT vcx9k9q81e62zd AT balu DOT cs DOT uni-paderborn DOT de> <AANLkTilzhFauWZU65g9oXxtwHBXqD60bCw2AKqa32yMd AT mail DOT gmail DOT com> <AANLkTinP4qnz3y9OkPAKQjzy9jAMsCbNBoamAjBiPjS- AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<AANLkTinP4qnz3y9OkPAKQjzy9jAMsCbNBoamAjBiPjS-@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On May 20 11:43, Huang Bambo wrote:
> 2010/5/20 Huang Bambo <bambo DOT huang AT gmail DOT com>:
> >> Huang,
> >>
> >> you - as the person who first saw and documented the problem in public
> >> (thank you!) - are in the best position to test it, if you can recreate the
> >> original situation (with the GBK(?) directory names).
> >>
> >> It would be beneficial to all of us, and you would be doing everybody a
> >> favour (if you wish, which is your choice), if you could test if the problem
> >> reproduces with Cygwin 1.7.5, and goes away with the snapshot.
> >
> > fork() now work well but find new problem after use the 0518 patch.
> > Usually I use mintty to as the default term tool. After use this patch, I can't
> > directly use mintty to open the first shell( like nothing happened), I
> > must use Cygwin.bat to create
> > a fist shell, then use short cut of mintty in the start menu to open others.
> >
> > I'll find out why if I have time.
> 
> terminate while calling forkpty().

I'm using mintty with the latest from CVS and I can't reproduce this.
Mintty starts just fine from a shortcut with target
"C:\cygwin\bin\mintty.exe -".


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

- Raw text -