delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2001/10/31/16:56:41

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, 31 Oct 2001 16:54:34 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: "make -j2" hang is not fixed in current repository
Message-ID: <20011031165434.A10999@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20011031182318 DOT 15582 DOT qmail AT lizard DOT curl DOT com> <20011031143547 DOT A10143 AT redhat DOT com> <20011031200818 DOT 11562 DOT qmail AT lizard DOT curl DOT com>
Mime-Version: 1.0
In-Reply-To: <20011031200818.11562.qmail@lizard.curl.com>
User-Agent: Mutt/1.3.21i

To clarify my last email:

- What I tried to convey is that recent events have made it less than
  likely that I will be fixing major bugs that require immense amounts of
  time to track down.

- I also expressed dismay that the bug-report/bug-fix ratio is not
  very close to 1 on the cygwin-developers mailing list.

- I provided a pointer to my original message so that you could refresh
  yourself with whatever vague explanation I gave about how I thought
  I'd originally fixed the problem.

- I vented on how much I hate getting stack traces in email.  I've
  just told Corinna something similar in personal email, in fact.

- And, finally, I was stated the obvious.  It has been more than a
  month since I suggested that this was fixed.  I'm not completely fresh
  on what I did so I can't offer the insight now that I could have
  potentially offered then.

Those were my five points.

You *are* *obviously* trying to fix bugs.  I am sure that I am sending
you mixed messages when I fix the bugs that you are working on.  I try
to explain what I've done when I do fix the bugs so that it is obvious
why I did what I did.  However, I am sure that it must be frustrating,
regardless.

(I actually went through a similar scenario with Kazuhiro.  I felt bad
because he often sent in fixes which I thought were not quite right.  I
ended up redoing things more to "my liking'.

Strangely, I haven't had to do that much lately.  I think that is a
sign that this crude feedback relationship worked.)

Your extremely detailed bug reports are appreciated.  This last one,
however, had more raw information than I am prepared to digest.  It was
200+ lines, the majority of which was stack trace.

You state that you are not qualified to fix this problem but I have to
differ with you.  You are obviously a *very* sharp person.  I really
don't believe that the cygwin source code is beyond you.  Your recent
analyses of problems have been impressive.

However, you may not have time to fully grok and debug this particular
problem and, as I have said, that is understandable.

The bottom line is that maybe this is just a bug that is not going to
get fixed.  I've noted this before.  It's a shame because I thought I
actually had finally squashed the problem after your last bug report but
I guess that I was overly optimistic.

Although, I'm now on iteration 53 of a full -j2 build of the winsup
directory without any pauses.  That particular test case couldn't get
much beyond 17 on my (733MHZ SMP W2K) system before.  So, I've at
least ameliorated *a* problem.  Apparently it wasn't your problem.

cgf

- Raw text -


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