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: <38BA1A28.93A03DDD@ece.gatech.edu>
Date: Mon, 28 Feb 2000 01:48:08 -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> <38B9BA99 DOT 5C4B3728 AT ece DOT gatech DOT edu> <20000227212444 DOT A11989 AT cygnus DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Chris Faylor wrote:
> 
> My understanding was that, in this case, the problem was not that bash
> was inoperable.  It was that it was using a lot of CPU time.  That's
> doesn't mean that it isn't working.  Also, AFAICT, gdb should still work
> in this scenario even if bash is broken.

Well, in *my* case, bash hung forever while reading the .bashrc files,
AND used 100% CPU. The worst of both worlds.

> 
> Anyway, the way that I debug the DLL is to put gdb and a "working" dll
> in the same directory and then use that to debug a broken dll.  Since
> Windows will find a DLL in the same directory as the executable, this
> works fine.
> 

I did not know this. There have been so many warnings about "don't ever
ever ever even *think* about having multiple cygwin.dll's on your
system" that it never occurred to me.

> You can also get debugging output from the strace program.
> 
> >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.
> 
> Well, all you, or anyone, had to do was ask.

Yep. that is true.

--Chuck

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