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, 16 Jan 2003 11:11:13 -0500 From: Christopher Faylor To: Nick Clifton Cc: Brian Ford , cygwin@cygwin.com, binutils@sources.redhat.com, dave@beermex.com Subject: Re: Support for DDWARF-2 debug info? (on cygwin) Message-ID: <20030116161113.GG30708@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Nick Clifton , Brian Ford , cygwin@cygwin.com, binutils@sources.redhat.com, dave@beermex.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i On Thu, Jan 16, 2003 at 03:58:09PM +0000, Nick Clifton wrote: >Hi Brian, > >> My current problem is that all previous DWARF2 implementations >> assign a VMA of zero to the .debug_* sections in the link script. >> This violates the PE format and makes the executable unusable. > >I saw your post about this to the binutils list. > >Does the PE format require that the debugging sections be loaded into >memory when the executable is invoked ? I didn't think that STABS debug information was loaded into memory. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/