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: Wed, 29 Aug 2001 12:14:19 -0400
From: Jason Tishler <jason AT tishler DOT net>
To: cygwin-developers AT cygwin DOT com
Subject: Re: still can't duplicate rxvt problem
Message-ID: <20010829121419.A820@dothill.com>
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010829090223.A3834@redhat.com>
User-Agent: Mutt/1.3.18i

Chris,

On Wed, Aug 29, 2001 at 09:02:23AM -0400, Christopher Faylor wrote:
> On Wed, Aug 29, 2001 at 08:59:32AM -0400, Jason Tishler wrote:
> >On Wed, Aug 29, 2001 at 12:12:35AM -0400, Christopher Faylor wrote:
> >> I still can't duplicate the rxvt problem.
> >
> >Are you referring to the problem that I reported?  If so, would you be
> >willing to try with my .bash_profile files if I post them?
> 
> I guess so.

You can find my .bash_profile files at:

    http://www.tishler.net/jason/misc/profile.tar.gz

Please backup your .bash_profile, .bashrc, and /etc/profile before
extracting the above into your home directory:

    $ cd
    $ tar -Pxzf /tmp/profile.tar.gz

You will also have to execute the following:

    $ mv .bash_profile-althea .bash_profile-$(uname -n)
    $ mv .bashrc-althea .bashrc-althea-$(uname -n)

before attempting to reproduce the problem.

> >> Is anyone who can duplicate it willing to do the tedious "binary search
> >> through cvs versions thing to see when it first occurred?
> >
> >I'm willing to try.  Unfortunately, this problem may have been lurking for
> >a long time.  IIRC, I only started to notice this around the time that
> >Cygwin bash 2.05 was released by Corrina (around 5/01) and I started
> >to go (bash) command completion happy --  causing me to add two more
> >command substitutions.
> 
> So, you're saying that this fails in 1.3.2, also?  I think that is
> new information.

I was able to reproduce the problem with 1.3.2:

    C:\home\jt>bash --login
    CYGWIN_NT-5.0 ALTHEA 1.3.2(0.39/3/2) 2001-05-20 23:28 i686 unknown
    ...
    TERM (rxvt) =
    althea[~]
    $ id
    althea[~]
    $ uid=1000(jt) gid=513(None) groups=0(Everyone),513(None),544(Administrators),545(Users),1001(Daemons)
    logout

Note the following:

1. My prompt is two line.
2. The prompt appears before the output of id.

Also, I have *not* been able to reproduce the bash --login problem via
rxvt under 1.3.2 (yet).  Go figure...

> >I'm also willing to post (compressed) strace logs of a good and bad test
> >run for perusal.  The compressed logs are about 128 KB each so I can put
> >them on my web site for download if that is preferred.
> 
> The URL is preferable.

The strace logs are available at:

    http://www.tishler.net/jason/misc/bash.log.bz2
    http://www.tishler.net/jason/misc/bash2.log.bz2
    http://www.tishler.net/jason/misc/bash3.log.bz2

Note the following:

1. bash.log.bz2 and bash2.log.bz2 are traces when bash logs out
2. bash3.log.bz2 is a trace when bash does *not* log out

Thanks,
Jason