Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Date: Thu, 20 Jan 2005 12:47:33 -0800 From: Joshua Daniel Franklin Reply-To: Joshua Daniel Franklin To: cygwin AT cygwin DOT com Subject: Re: cygwin bughunt (FAQ alert?) In-Reply-To: <20050120200455.GK9369@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <79F81D5F4790D344B05F489CE2AC8AB7109544 AT dubexdc03 DOT dubex DOT net> <20050120200455 DOT GK9369 AT trixie DOT casa DOT cgf DOT cx> X-IsSubscribed: yes > 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/ -- 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/