Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Benjamin Kosnik <bkoz@redhat.com>, gdb@sources.redhat.com
Subject: Re: can't find class named `foo', as given by C++ RTTI
Date: Sat, 30 Jun 2001 10:14:00 -0000	[thread overview]
Message-ID: <np1yo1sxc6.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <13482076.993868984@[192.168.0.106]>

Daniel Berlin <dan@cgsoftware.com> writes:
> But first, realize that to implement in GDB, you must do one of two things.
> 1. Change GDB to only explicitly keep track of the current scope (IE like 
> the compilers do), and magically have the symbols for that scope.  This 
> would require so much redesign it's not even funny.
> 2. Convert what the designs say from stacks to blockvectors (IE most are 
> based on stacks where you only keep the current visible scopes around.  We 
> need all the scopes, so you just have to think of how to do the conversion 
> between the two in your head. It's usually not that difficult to do at all.)
> 
> I'd suggest, for obvious reasons, 2.

Yeah, I'd say 1. doesn't apply to us. 

> Section 3 of Advanced Compiler Design and Implementation - Steven Muchnick
> 
> It's titled "Symbol table structure".

Oh, I've got that, actually.


  reply	other threads:[~2001-06-30 10:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-27 21:55 Benjamin Kosnik
2001-06-27 22:25 ` Daniel Berlin
2001-06-27 22:51   ` Benjamin Kosnik
2001-06-27 23:26     ` Daniel Berlin
2001-06-28  1:37       ` Benjamin Kosnik
2001-06-27 23:06   ` Daniel Berlin
2001-06-28  1:32     ` Benjamin Kosnik
2001-06-28 16:02       ` Daniel Berlin
2001-06-28 16:14         ` Benjamin Kosnik
2001-06-29 15:14     ` Jim Blandy
2001-06-29 23:43       ` Daniel Berlin
2001-06-30 10:14         ` Jim Blandy [this message]
2001-06-29 11:15 ` Jim Blandy
2001-06-29 11:20   ` Daniel Berlin
2001-06-29 11:34     ` Benjamin Kosnik
2001-06-29 11:38   ` Daniel Berlin

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=np1yo1sxc6.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=bkoz@redhat.com \
    --cc=dan@cgsoftware.com \
    --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