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
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 <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: cygwin AT cygwin DOT com
cc: Nick Clifton <nickc AT redhat DOT com>, <binutils AT sources DOT redhat DOT com>,
   <dave AT beermex DOT com>
Subject: Re: Support for DDWARF-2 debug info? (on cygwin)
In-Reply-To: <20030116161113.GG30708@redhat.com>
Message-ID: <Pine.GSO.4.44.0301161044390.12926-100000@eos>
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/