From: Daniel Jacobowitz <drow@false.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sourceware.org
Subject: Re: stabs difference gcc 2.95.3 -> 3.4.3
Date: Thu, 30 Mar 2006 21:52:00 -0000 [thread overview]
Message-ID: <20060330152033.GA31520@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20060330162459.01fbe008@NT_SERVER>
On Thu, Mar 30, 2006 at 04:33:11PM +0200, Fabian Cenedese wrote:
> Well, as the currently used compiler 2.95.3 is even older and I supposed
> that the stabs format should be compatible I didn't especially try the
> newest versions but I may now.
The C++ front end has gotten much more sophisticated. Namespace
debugging works in DWARF-2, but fails badly in stabs.
> The -g is given to gcc, I don't know if that gets passed on to as. But so
> was the setup with the older compiler as well, where it worked.
GCC 2.95.x predates assembler -g support; GCC 3.4.x doesn't.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-30 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 14:00 Fabian Cenedese
2006-03-30 15:20 ` Daniel Jacobowitz
2006-03-30 18:22 ` Fabian Cenedese
2006-03-30 21:52 ` Daniel Jacobowitz [this message]
2006-03-31 14:01 ` Fabian Cenedese
2006-03-31 14:20 ` Daniel Jacobowitz
2006-04-03 8:40 ` Fabian Cenedese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060330152033.GA31520@nevyn.them.org \
--to=drow@false.org \
--cc=Cenedese@indel.ch \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox