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 17:00:04 -0500 From: "Pierre A. Humblet" To: cygwin@cygwin.com Subject: Re: cygwin bughunt (FAQ alert?) Message-ID: <20050120220004.GA67407@Worldnet> 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 12:47:33PM -0800, Joshua Daniel Franklin wrote: > > 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/ This must be modulated by the warnings on the snapshot page, so I would recommend an initial step: write to the list, describe the bug and ask for a recommended snapshot. Should we also provide an optional cygwin_debug package, with only an unstripped cygwin1.dll.debug ? Pierre -- 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/