Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Joel Brobecker <brobecker@ACT-Europe.FR>, gdb-patches@sources.redhat.com
Subject: Re: .n suffixes for function names in stabs debug info (GCC 3.1-based compiler)
Date: Tue, 16 Apr 2002 06:06:00 -0000	[thread overview]
Message-ID: <1018962390.14863.12.camel@dberlin.org> (raw)
In-Reply-To: <20020412103435.A24938@nevyn.them.org>

> 
> Jim, that raises one question.  How are we going to support searching
> for a name in all scopes, a la `info func'?  It seems that it might be
> prohibitively more expensive than it is currently...

I'm not so sure it would be all that more expensive, but if it was, we
could just throw all names into a global ternary search tree, and use
that for searches against all scopes.

For the example of "info func main", you just walk the tree to main, and
print out all children from there.


      reply	other threads:[~2002-04-16 13:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11  9:19 Joel Brobecker
2002-04-11 12:04 ` Daniel Jacobowitz
2002-04-12  1:28   ` Joel Brobecker
2002-04-12  1:43   ` Joel Brobecker
2002-04-12  7:34     ` Daniel Jacobowitz
2002-04-16  6:06       ` Daniel Berlin [this message]

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=1018962390.14863.12.camel@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=brobecker@ACT-Europe.FR \
    --cc=drow@mvista.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