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
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: Re: maintaining bash
Date: Sun, 10 Apr 2005 03:40:12 +0200
Message-ID: <79F81D5F4790D344B05F489CE2AC8AB717CF38@dubexdc03.dubex.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "David Dindorp" <ddi AT dubex DOT dk>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j3A1eYnx004565

Dave Korn wrote:
>>>> If you can tell me how to proceed from here, I'd be happy to throw
>>>> in a bunch of manhours to try and find out what's wrong.
>>> 
>>>   http://cygwin.com/acronyms#PPAST
>> 
>> Obviously, if I were able to produce a simple testcase, I would have.
>> Duh ;-).
> 
> There's nothing _obvious_ about that at all.  It would be a false
> inference on my part to try and deduce that, because you have not
> PPASTed before, you would necessarily be unable to do so in the
> future.[*]

Inference, schminference.
I have posted a test case in the past, so your point is moot.

I consider it common sense to PPAST if you can, but believe me, in this
situation it's pretty darn hard.


> Furthermore, it seems to me that if you have some manhours to spend,
> but not the lifetimes you feel it would require to get to grips with
> debugging the problem at a deep level,

I've tried my best to give out all the information I could in the
postings I've made to this group, and I've received no help. Except for
a (very kind, thank you) explanatory e-mail from you on stack traces.

With that "no help" mentioned going in my direection, I'd have to get to
a deep level not of my problem as you mention, but of Cygwin.  Cygwin is
as complex as a Linux kernel.  That's a pretty big task if you ask me.

> then spending those hours trying
> to create a simple testcase might be the most productive use you could
> put them to.

It's just not possible.

Somewhat paradoxical, the only way I can prove to you that THAT's true
is for you to actually try and DO produce a test case; whereafter you
will come to the conclusion that your words were hasty and your skills
insufficient.

If your fingers are itching for mathematical proof that I'm not lying
about the impossibility of producing a test case, I can probably get
you remote access to a test box ;-).

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