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 X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Thu, 16 Jan 2003 10:45:08 -0600 (CST) From: Brian Ford X-X-Sender: ford@eos To: cygwin@cygwin.com cc: Nick Clifton , , Subject: Re: Support for DDWARF-2 debug info? (on cygwin) In-Reply-To: <20030116161113.GG30708@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 16 Jan 2003, Christopher Faylor wrote: > On Thu, Jan 16, 2003 at 03:58:09PM +0000, Nick Clifton wrote: > >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. > That's true. It is not. See my previous post. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/