Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <38B9BA99.5C4B3728@ece.gatech.edu>
Date: Sun, 27 Feb 2000 19:00:25 -0500
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Undefined reference to '_ctype_'?
References: <20000225132218 DOT 5282 DOT qmail AT web110 DOT yahoomail DOT com> <20000225145103 DOT SM00161 AT KENDALLB> <20000226040630 DOT A21594 AT shell4 DOT ba DOT best DOT com> <20000227154653 DOT A7573 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris,

  You make a number of very good points in your recent message, and
I both sympathize and agree with your stance. However, I am one of 
the folks who sent in a "bash is using 100% CPU" reports with no
debugging information.

> This week, I have spent considerable time trying to track down the
> various "bash is taking all of my CPU" problems despite the almost total
> lack of debugging information offered by any of the people reporting the
> problem.
> 

I would have liked to send in debugging info -- but had no idea how to
do it. If I can't run bash, then I cannot run gdb either. Since the
native (microsoft-supplied) debugging tools are so poor, and cygwin-gdb
is not accessible, debugging a bash-related problem is quite a
challenge. 
It's possible I suppose to use a mingw-based gdb to debug the
cygwin-based
bash, but I don't have mingw setup on my machine.

Anyway, that's my "excuse". I'm sure that many others were in the same
boat -- they wanted to help and wanted to provide useful debugging info.
But the failure (bash) was in the critical path for obtaining that info.
NOTE to others on the list: please, don't clutter the list with me-too
messages, even if this description matches your experience.

> 
> For now, you're stuck with the volunteer efforts of myself, DJ, Corinna,
> Mumit, Sergey, Ron Parker, and a few others.  I don't expect that that
> will change any time soon, although, FWIW, you'll soon be seeing a
> "@cygnus.com" appended to Corinna's email address.

And I greatly appreciate the efforts of all the core developers in
providing
and developing such a great tool. Thank you.

--Chuck Wilson

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com