Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa] generate symbols associated to namespaces
Date: Tue, 05 Aug 2003 18:18:00 -0000	[thread overview]
Message-ID: <yf2r840vugj.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20030805180839.GA30301@nevyn.them.org> (Daniel Jacobowitz's message of "Tue, 5 Aug 2003 14:08:39 -0400")

On Tue, 5 Aug 2003 14:08:39 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> On Tue, Aug 05, 2003 at 11:06:28AM -0700, David Carlton wrote:
>> On Tue, 5 Aug 2003 13:54:29 -0400, Daniel Jacobowitz <drow@mvista.com> said:

>>> Is there any particular reason not to use the global block?  If so
>>> might want to comment what it is.

>> Yes: we never want these symbols to be found by a normal search of
>> all symtabs' global blocks, because we don't trust these symbols.
>> We only want them found as a last resort, once we've looked every
>> place that symbols associated to classes should live.  So that's
>> why I stash them in a local block.  I'll add a comment to that
>> effect.

> OK.  I would have thought that the fake symtab would never have been
> searched normally, though - I guess it gets chained into
> objfile-> symtabs?

Yeah, allocate_symtab does that automatically.

I'm a little tempted not to have a symtab there at all, instead just
having a special block (or even a special dictionary) that isn't
associated to a symtab.  That, however, runs into the issue of what to
do with the 'symtab' argument to lookup_symbol in that case; we could
set it to NULL, but in that case GDB might crash if some silly user
typed 'break NamespaceName'.  Or something.

David Carlton
carlton@kealia.com


  reply	other threads:[~2003-08-05 18:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 20:22 David Carlton
2003-06-22 17:42 ` Daniel Jacobowitz
2003-06-24 19:00   ` David Carlton
2003-06-24 19:02     ` Daniel Jacobowitz
2003-06-27 16:04       ` David Carlton
2003-06-27 21:58         ` David Carlton
2003-06-27 22:32           ` David Carlton
2003-08-05 16:30           ` David Carlton
2003-08-05 17:54           ` Daniel Jacobowitz
2003-08-05 18:06             ` David Carlton
2003-08-05 18:08               ` Daniel Jacobowitz
2003-08-05 18:18                 ` David Carlton [this message]
2003-08-31 19:29             ` Daniel Jacobowitz
2003-09-02 16:38               ` David Carlton
2003-09-09 19:42           ` Elena Zannoni
2003-09-09 20:28             ` David Carlton
2003-09-09 22:17               ` Elena Zannoni
2003-09-09 23:25                 ` David Carlton
2003-09-11 19:52                   ` David Carlton
2003-09-17 20:41                     ` David Carlton
2003-09-11 23:28             ` [rfa] use allocate_block more David Carlton
2003-09-11 23:33               ` Elena Zannoni
2003-09-11 23:44                 ` 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=yf2r840vugj.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb-patches@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