Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Hilfinger@otisco.mckusick.com
Cc: drow@mvista.com, gdb@sources.redhat.com, ezannoni@redhat.com,
	jimb@redhat.com
Subject: Re: [rfc] lookups with natural/linkage names
Date: Tue, 27 May 2003 15:55:00 -0000	[thread overview]
Message-ID: <ro1wugc75av.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <200305261042.h4QAgxc07019@otisco.McKusick.COM>

On Mon, 26 May 2003 03:42:59 -0700, "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com> said:

> Are nested function names ever mangled?  We seldom consider nested
> functions, because they don't occur in official C/C++, but they do
> occur in GCC's extensions (and in Pascal and Ada).  On IRIX, using
> Dwarf-2, nested function names do NOT appear in the minimal symbols
> (whereas on Linux, they do).  I hope you see why this makes me
> slightly nervous.

Eep.  I hadn't thought of that case.

Still, I don't see why there would be a particular reason to mangle
names of nested functions.  The point of mangling is to communicate
rich information about an object over an information channel whose
format is tightly constrained.  But for local objects, you can use the
debug info as the information channel, and its format is very rich.
So information about, say, types of arguments to nested functions can
(and should, in my reading of DWARF 2, though I admit that the
standard is annoyingly vague about names) be transmitted in other
parts of the debug info, not in the name attribute.

Having said that, there's still the question of whether or not GDB
currently depends on getting information from the mangled name.  And
the answer is that, currently, it does that to an extent that is
probably unhealthy.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2003-05-27 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-23 23:48 David Carlton
2003-05-24  8:11 ` Paul N. Hilfinger
2003-05-24 14:36   ` Daniel Jacobowitz
2003-05-26 10:43     ` Paul N. Hilfinger
2003-05-27 15:55       ` David Carlton [this message]
2003-05-24 21:10   ` David Carlton

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=ro1wugc75av.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=Hilfinger@otisco.mckusick.com \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    /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