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
Date: Thu, 20 Jan 2005 16:29:36 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: cygwin bughunt (FAQ alert?)
In-Reply-To: <cb51e2e05012012475c668d43@mail.gmail.com>
Message-ID: <Pine.GSO.4.61.0501201627110.6491@slinky.cs.nyu.edu>
References: <79F81D5F4790D344B05F489CE2AC8AB7109544 AT dubexdc03 DOT dubex DOT net> <20050120200455 DOT GK9369 AT trixie DOT casa DOT cgf DOT cx> <cb51e2e05012012475c668d43 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 20 Jan 2005, Joshua Daniel Franklin wrote:

> > On Thu, Jan 20, 2005 at 08:12:31PM +0100, David Dindorp wrote:
> > >Tracking it down with GDB to cygwin_split_path() : 0x61073e06 was easy.
> >
> On Thu, 20 Jan 2005 15:04:55 -0500, Christopher Faylor wrote:
> > Since cygwin isn't built with debugging symbols, the symbols that you do
> > see in gdb are basically meaningless.
> >
> > I think this has come up often enough to be a FAQ.  Joshua?
> >
> > In any event, you do need to either build a debugging version or, possibly,
> > use a snapshot from http://cygwin.com/snapshots/ since those are currently
> > built with debugging turned on.
>
> Sure, how about this:
>
> I've found a bug in Cygwin, how can I debug it?
>
> Debugging symbols are stripped from distibuted Cygwin binaries, so any
> symbols that you see in gdb are basically meaningless. It is also a good
> idea to use the latest code in case the bug has been fixed, so you will
> need to either build your own debugging version by following the
> instructions at http://cygwin.com/faq/faq_3.html#SEC102 or use a current
> snapshot from http://cygwin.com/snapshots/

The entry is good, but the title implies (*GASP*) that there may be bugs
in Cygwin.  I'd suggest something like "I'm debugging within the Cygwin
DLL space, and gdb shows garbage symbols.  How do I debug Cygwin?"
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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