From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Petr Sorfa <petrs@caldera.com>, gdb <gdb@sources.redhat.com>
Subject: Re: adding namespace support to GDB
Date: Fri, 23 Aug 2002 11:47:00 -0000 [thread overview]
Message-ID: <20020823184746.GA25528@nevyn.them.org> (raw)
In-Reply-To: <ro1wuqhju4d.fsf@jackfruit.Stanford.EDU>
On Fri, Aug 23, 2002 at 11:41:06AM -0700, David Carlton wrote:
> In article <3D6677D3.6E84743C@caldera.com>, Petr Sorfa
> <petrs@caldera.com> writes:
>
> > Well to help things along I will be submitting a DWARF patch that
> > will supported imported declarations which are essential for FORTRAN
> > modules and C++ namespaces.
>
> Great, I look forward to reading it.
>
> > This is essential for the "using" commands in either language (of
> > course the compiler needs to generate the correct DWARF
> > ;o)).
>
> Yes, well, there is always that. Certainly it seems like a solution
> for C++ will initially have to get recreate namespace info from
> DW_AT_MIPS_linkage_name, and there's no way that we'll be able to
> allow users to use symbol names as if all the appropriate using
> directives were in effect, since that information simply isn't in the
> debug information that GCC is currently producing. (Though that's not
> the end of the world: we should be able to do name lookup using C++'s
> name resolution rules based on the enclosing function and its
> arguments, presumably.)
C++ certainly does _not_ need to reconstruct from
DW_AT_MIPS_linkage_name. Everything we need should be there in
DW_TAG_namespace and DW_TAG_structure/class markers; I have patches to
use this information, with the caveats I noted in my other message.
I am gradually working on removing all uses of the physname from the
C++ debugging code. It's a hack (and a space waste!).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-23 18:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 8:42 David Carlton
2002-08-23 10:46 ` Petr Sorfa
2002-08-23 11:41 ` David Carlton
2002-08-23 11:42 ` Daniel Berlin
2002-08-23 12:26 ` Petr Sorfa
2002-08-23 15:35 ` Daniel Berlin
2002-08-26 16:20 ` Petr Sorfa
2002-08-26 17:32 ` Daniel Berlin
2002-08-27 14:04 ` Petr Sorfa
2002-08-23 11:47 ` Daniel Jacobowitz [this message]
2002-08-23 11:48 ` Daniel Berlin
2002-08-23 12:20 ` Daniel Jacobowitz
2002-08-23 12:24 ` David Carlton
2002-08-23 15:32 ` Daniel Berlin
2002-08-23 15:37 ` Jason Molenda
2002-08-23 12:20 ` David Carlton
2002-08-23 11:05 ` Daniel Jacobowitz
2002-08-23 14:26 ` Daniel Jacobowitz
2002-08-23 17:19 ` David Carlton
2002-08-26 9:56 David Anderson
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=20020823184746.GA25528@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--cc=gdb@sources.redhat.com \
--cc=petrs@caldera.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