Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Sat, 1 Sep 2001 13:58:37 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: still can't duplicate rxvt problem -- new information (Corinna please note)
Message-ID: <20010901135837.A22811@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20010901132427 DOT A22570 AT redhat DOT com> <20010901134704 DOT E1148 AT dothill DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010901134704.E1148@dothill.com>
User-Agent: Mutt/1.3.21i

On Sat, Sep 01, 2001 at 01:47:04PM -0400, Jason Tishler wrote:
>On Sat, Sep 01, 2001 at 01:24:27PM -0400, Christopher Faylor wrote:
>> Ok.  I think I've finally figured this out from inspecting the enclosed strace
>> logs and looking at bash sources.  I haven't tried to duplicate this myself
>> yet but I may get to doing that sometime today.  In the meantime...
>>
>> [snip]
>
>Thanks for investigating this problem.  Unfortunately, I won't be able
>to get to this until after the holiday.  However, I will start on it
>first thing Tuesday morning and report back to the list ASAP.

Actually, I finally did download your environment and managed to
duplicate the problem.  The change to bash seems to fix it.  I saw
the problem after only a couple of tries without the bash change
and I couldn't duplicate it after 30 tries with the change.

Corinna, would you mind making a new bash release with my previous
configure change?  It should be pretty harmless even if it doesn't
actually fix the problem.

Btw, I noticed that I couldn't rebuild bash from the sources in latest
due to missing _distribution and _patchlevel files.  I had to copy those
from Red Hat's internal CVS version of bash.

cgf