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
Message-ID: <cb51e2e05012023056d75d98@mail.gmail.com>
Date: Thu, 20 Jan 2005 23:05:08 -0800
From: Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
Reply-To: Joshua Daniel Franklin <joshuadfranklin AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bughunt (FAQ alert?)
In-Reply-To: <20050121002403.GE12628@trixie.casa.cgf.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <79F81D5F4790D344B05F489CE2AC8AB7109551 AT dubexdc03 DOT dubex DOT net> <20050121002403 DOT GE12628 AT trixie DOT casa DOT cgf DOT cx>
X-IsSubscribed: yes

On Thu, 20 Jan 2005 19:24:03 -0500, Christopher Faylor wrote:
> However, oops, this means that the advice of using a snapshot shouldn't
> go into the FAQ since this isn't a permanent arrangement.

Well, how about this then:

I may have found a bug in Cygwin, how can I debug it (the symbols in gdb 
look funny)?

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 follow the 
instructions at http://cygwin.com/faq/faq_3.html#SEC102 to build your own 
debugging version. You can also contact the mailing list for pointers
(a simple test
case that demonstrates the bug is always welcome).

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