delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/02/28/14:03:04

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date: Mon, 28 Feb 2005 14:01:56 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bughunt (snapshot)
Message-ID: <20050228190156.GA32295@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <79F81D5F4790D344B05F489CE2AC8AB7146D67 AT dubexdc03 DOT dubex DOT net>
Mime-Version: 1.0
In-Reply-To: <79F81D5F4790D344B05F489CE2AC8AB7146D67@dubexdc03.dubex.net>
User-Agent: Mutt/1.4.1i

On Mon, Feb 28, 2005 at 07:44:46PM +0100, David Dindorp wrote:
>Cristopher Faylor wrote:
>>David Dindorp wrote:
>>>Bash seems to think that it's child has terminated prematurely.
>>>Has anyone experienced something similar?
>>>
>>>Evidence: See the order of execution in the script below,
>>>compare with what bash does (further below).
>>
>>>Version: snapshot 20050226 / bash 3.0.
>>
>
>[...]
>
>>It's difficult to see how this could be an actual run
>>of the above script.
>
>I snipped irrelevant parts of the output, eg. long paths.
>(FYI, the original log file is ~ 341.000 lines of output.)
>
>[...]
>
>>What happened to the leading slash?
>
>Busted!  Damn...
>
>[...]
>
>>FWIW, when I try this, everything works as expected.  It's difficult
>>to see how this could be executed out of order unless your tar
>>and/or sleep are not standard cygwin programs.
>
>It does work 90% of the time.
>Under Cygwin 1.5.10, the problem is also there, and *MUCH* worse.
>
>tar.exe, gzip.exe and sleep.exe are from *cough* 1.5.10 *cough*.
>I was told that it doesn't matter as long as the Cygwin DLL
>is a fresh nightly.  I'll replace them with 1.5.12-1's and catch
>the error again (prolly in a couple of days or so) if that's
>better?

There is no such thing as a "1.5.12-1 version" of tar.

You asked what you could do to report problems.  Being precise is one
thing you could do.  You could also provide cygcheck output as is
suggested by http://cygwin.com/problems.html .

Also, providing simple test cases which reproduce the problem would help.
I just wasted some time trying to reproduce your environment since I
assumed that you'd provided a script which could easily reproduce the
problem and that this was a problem which was specific to the snapshot.
Apparently that is not the case.

Anyway, this sounds a lot like the bash problem which has been discussed
here over the last several months (most heavily in the October time
frame).  If you aren't running bash-2.05b-17 then that's probably your
problem.

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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019