Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: Namespaces with gcc v3 stabs+?
Date: Thu, 05 Dec 2002 17:14:00 -0000	[thread overview]
Message-ID: <20021206011508.GB28778@nevyn.them.org> (raw)
In-Reply-To: <200212060031.gB60Vt517871@duracef.shout.net>

On Thu, Dec 05, 2002 at 06:31:55PM -0600, Michael Elizabeth Chastain wrote:
> Question for Daniel J or David C or Kevin B or anybody who knows
> about v3 and stabs support ...
> 
> I'm looking at disimprovements from gcc v2 to gcc v3.  One of the
> issues is that gcc 2.95.3 / stabs+ emits stab information
> for symbols in namespaces, but gcc 3.2.1 / stabs+ emits the stab
> information with the wrong name.

Erk.  Obviously GCC is wrong.  Just the name is not useful.

What do we want it to do, David?  If we're going to get stabs changed
in GCC anyway, we could get explicit namespace markers, and leave the
demangled name in the stabs.  That's parallel to the DWARF-2 approach.

> Kevin B had a similar issue in May 2002:
> 
>   http://gcc.gnu.org/ml/gcc-patches/2002-11/msg01661.html

Wrong URL, that's Daniel in November...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-06  1:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 16:31 Michael Elizabeth Chastain
2002-12-05 17:14 ` Daniel Jacobowitz [this message]
2002-12-06 11:25   ` David Carlton
2002-12-05 18:06 Michael Elizabeth Chastain
2002-12-06 13:06 Michael Elizabeth Chastain
2002-12-06 17:27 ` David Carlton
2002-12-07  6:49   ` Stan Shebs
2002-12-09 10:59     ` David Carlton
2002-12-06 17:58 ` Daniel Jacobowitz
2002-12-06 19:48 Michael Elizabeth Chastain

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=20021206011508.GB28778@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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