This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Which .stabs to use? (please help)


> Date: Tue, 31 Jul 2001 04:31:51 +0200
> From: Carlo Wood <carlo@alinoe.com>
> Cc: gcc@gcc.gnu.org
> Content-Disposition: inline
> User-Agent: Mutt/1.2.5i
> X-OriginalArrivalTime: 31 Jul 2001 02:31:53.0260 (UTC) FILETIME=[F5B41EC0:01C11968]
> 
> On Mon, Jul 30, 2001 at 10:16:58AM -0700, Geoff Keating wrote:
> > 
> > This is the same problem as the one with dwarf information, which is
> > much more serious because the dwarf information is used for
> > exception-handling.
> > 
> > After some discussion, I believe we decided that the right thing to do
> > for the dwarf information was to
> > 
> > (a) fix the linker so that it could handle (b), and then
> > (b) output the dwarf information that's used for EH in linkonce sections.
> > 
> > Could something similar be done for stabs?
> 
> Not without breaking all existing debuggers imho.
> The stabs info needs to go into the .stabs section.

Well, since existing debuggers are already broken, there's not much to
be done about it.

> Hopefully this problem will go away once we use precompiled headers.
> HURRY UP with those precompiled headers! ;)

No, precompiled headers do not change the compiler's output.

-- 
- Geoffrey Keating <geoffk@geoffk.org>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]