X-Spam-Check-By: sourceware.org Date: Fri, 16 Mar 2007 13:53:06 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Using cygwin1.dbg Message-ID: <20070316175306.GA781@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <45FAC9DD DOT 2050804 AT cwilson DOT fastmail DOT fm> <20070316170808 DOT GB30058 AT trixie DOT casa DOT cgf DOT cx> <45FAD896 DOT 9080304 AT cwilson DOT fastmail DOT fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45FAD896.9080304@cwilson.fastmail.fm> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri, Mar 16, 2007 at 12:49:10PM -0500, Charles Wilson wrote: >Christopher Faylor wrote: >>On Fri, Mar 16, 2007 at 11:46:21AM -0500, Charles Wilson wrote: >>>Or should I just build the kernel unstripped using cygwin-1.5.24-2-src, >>>and debug against that? >> >>Corinna has been responsible for the last few cygwin 1.5.2x releases and >>she has a different way of generating a release than mine. It's >>possible that the .dbg file isn't working right or created correctly. > >This seems to be the case. I finished a build of cygwin-1.5.24-2 (with >CFLAGS="-g -O0") but > > (1) the build process seems automatically to strip the dll, and >produce a detached .dbg file. > > (2) I got the similar behavior using my .dll/.dbg combo as I got with >the "official" pair from 1.5.24-2: popups -- but then insight died on >me. FWIW, my .dbg file is much smaller than the official one: 350k vs. >9.5M. > >Is it even possible anymore to create an "old-style" debugging >cygwin1.dll, with integrated rather than detached debug symbols? No. 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/