Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <6A0F951DBB1DD611A90600805F9F54550282D7E6@mail.empirecorp.org>
From: SMore AT empirecorp DOT org
To: cygwin AT cygwin DOT com
Subject: RE: cygwin1-20031218.dll.bz2 and rxvt
Date: Tue, 23 Dec 2003 14:24:37 -0500
MIME-Version: 1.0
Content-Type: text/plain

Great news !!! 

I am no longer getting a stackdump (using rsync + ssh) with the latest
snapshot: cygwin-inst-20031223.tar.bz2.

Thanks for your work.
-Steve More

-----Original Message-----
From: Christopher Faylor
[mailto:cgf-no-personal-reply-please AT cygwin DOT com]
Sent: Tuesday, December 23, 2003 11:48 AM
To: cygwin AT cygwin DOT com
Subject: Re: cygwin1-20031218.dll.bz2 and rxvt


On Thu, Dec 18, 2003 at 03:22:10PM -0500, Christopher Faylor wrote:
>On Thu, Dec 18, 2003 at 02:31:40PM -0200, Fr?d?ric L. W. Meunier wrote:
>>At least here rxvt dies after started. cmd.exe works. Latest
>>Cygwin packages on XP Professional SP1 + all updates.
>
>As luck would have it, this is due to a change that I made to allow me
>to track down the other 'rsync segvs' problem.  I think I understand it
>now.  It's in a section of cygwin code that I've always tried to avoid.
>Guess I don't have that luxury anymore...

Well, one massive rewrite later, I am uploading a new version of cygwin.
I've tried it with rxvt, zsh, ssh, and inetd.  I'm sure I've forgotten
something, though.

Please give today's snapshot a try.

cgf

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

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