Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: adding namespace support to GDB
Date: Fri, 23 Aug 2002 11:05:00 -0000	[thread overview]
Message-ID: <20020823180635.GA20780@nevyn.them.org> (raw)
In-Reply-To: <ro1hehloa33.fsf@jackfruit.Stanford.EDU>

On Fri, Aug 23, 2002 at 08:42:40AM -0700, David Carlton wrote:
> I recently asked Daniel Jacobwitz for suggestions as to what I could
> do to help GDB, and he suggested that I might try adding proper
> namespace support.  I've skimmed a thread on the issue from early
> April with lots of interesting ideas; at some point, it sounded like
> Jim Blandy was about to start writing up some concrete possible
> interfaces, and I was wondering if anything more came of that.
> 
> For the time being, I'm going to reread that thread more closely, look
> at Petr Sorfa's module patch, look at the DWARF-3 standard, look at
> existing GDB code, and think about this for a while.  (Or at least I
> hope that's what I'm going to do: maybe I'll instead spend all of my
> time arguing with Stanford's benefits office.  Anybody know of any
> interesting free software jobs in countries with nationalized health
> insurance?)  But I don't want to duplicate effort if somebody else has
> already started working on this.

Meanwhile, I'm working on ugly namespace support - without all the
symbol table and scoping work that we'll need to make things quite
"correct", I'm trying to make the debug readers provide scope
information (mostly done) and the rest of GDB cope with it
(investigating).  I have patches for both stabs and DWARF-2 to generate
class and types names properly qualified, but because the rest of GDB
doesn't expect this they never get unqualified; we get things like

  std::bar std::bar::function(std::bar&)

because it doesn't know that the std:: can be elided.  Etc.

Hope to have more time to work on this next week.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2002-08-23 18:05 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
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 [this message]
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=20020823180635.GA20780@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.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