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 Date: Fri, 21 Jan 2005 13:15:53 +0100 From: Corinna Vinschen To: "'cygwin AT cygwin DOT com'" Subject: Re: cygwin bughunt (FAQ alert?) Message-ID: <20050121121553.GQ3113@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: "'cygwin AT cygwin DOT com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jan 21 11:18, Hughes, Bill wrote: > I don't think I'm putting this very well, but it may make the FAQ easier if > the standard advice is to load the snaphot and use that for debugging, it > removes a separate layer of potential problems in building the dll. I > suspect the people who would want a stripped snapshot to be more capable of > producing it than those would may need to build one with debug info. IMHO you're looking from the wrong direction. People capable of debugging the Cygwin DLL are usually also capable of building it. I'm wondering how somebody should be able to debug an application at all, if this person stumbles over using the compiler tools. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/