Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Thu, 16 Jan 2003 11:11:13 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: Nick Clifton <nickc AT redhat DOT com>
Cc: Brian Ford <ford AT vss DOT fsi DOT com>, cygwin AT cygwin DOT com,
   binutils AT sources DOT redhat DOT com, dave AT beermex DOT com
Subject: Re: Support for DDWARF-2 debug info? (on cygwin)
Message-ID: <20030116161113.GG30708@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: Nick Clifton <nickc AT redhat DOT com>,
	Brian Ford <ford AT vss DOT fsi DOT com>, cygwin AT cygwin DOT com,
	binutils AT sources DOT redhat DOT com, dave AT beermex DOT com
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0301160902220 DOT 12926-100000 AT eos> <m3fzrtozn2 DOT fsf AT north-pole DOT nickc DOT cambridge DOT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3fzrtozn2.fsf@north-pole.nickc.cambridge.redhat.com>
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/