Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 20 Jan 2005 16:35:21 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin bughunt (FAQ alert?) Message-ID: <20050120213521.GC11688@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <79F81D5F4790D344B05F489CE2AC8AB7109544@dubexdc03.dubex.net> <20050120200455.GK9369@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Thu, Jan 20, 2005 at 04:29:36PM -0500, Igor Pechtchanski wrote: >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?" It is guaranteed that there are bugs in cygwin so I don't have any problems with using this terminology. However maybe it could be softented to something like "I may have found a bug in Cygwin..." An additional entry might be "Why do the symbols look funny when I try to debug Cygwin?" cgf -- 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/