Date: Tue, 25 Apr 2006 17:27:32 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Call for testing Cygwin snapshot
Message-ID: <20060425212732.GE18840@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20060425134320 DOT fb30e530d17747c2b054d625b8945d88 DOT 6a269b6ea8 DOT wbe AT email DOT secureserver DOT net> <055e01c668ad$b32316d0$a501a8c0 AT CAM DOT ARTIMI DOT COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <055e01c668ad$b32316d0$a501a8c0@CAM.ARTIMI.COM>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Tue, Apr 25, 2006 at 10:17:47PM +0100, Dave Korn wrote:
>On 25 April 2006 21:43, Jerry D. Hedden wrote:
>
>> Ernie Coskrey wrote:
>>> it's possible that Jerry has found a scenario that causes this problem to
>>> occur. Maybe not, but if he can reproduce it it would be worth checking.
>> 
>> I can reproduce the problem.  That's not the issue.  I cannot provide a
>> little test app to produce the problem at will.
>
>  Since nobody else is reporting this problem, it seems pretty unlikely that
>anyone else is going to be able to do it for you.
> 
>> As for the patch, that's useless - I'm not going to try to learn how to
>> build the Cygwin DLL.
>
>  In that case the P clearly EBKAC.
>
>>   However, if anyone can suggest some other
>> simple, non-labor-intensive method for gathering more data on this
>> problem, I'd be willing to give it a try.
>
>  Sounds like your best bet is to sit there and do nothing.  Yep, that's it.
>Thats's *bound* to get the bug fixed.  Why, surely sooner or later someone
>else will have the same bug and fix it for you?  All you have to do is just
>sit there and wait.  If you get bored watching the tumbleweed roll past, you
>could always read
>
>http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin
>
>to pass the time.

While I generally agree with the sentiment, in this case, I don't think
it would be productive to attempt a build of the DLL until I've verified
that I can't reproduce the problem with the supplied scripts.

And, I really don't think it's a good idea to start supposing reasons
for the hang yet unless someone wants to actually look at the
differences between the snapshots and propose a theory based on the
that.

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/