From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: [Fwd: gdb "call" very slow on large C++ program; 2 possible patches]
Date: Fri, 07 Dec 2001 09:30:00 -0000 [thread overview]
Message-ID: <20011207122951.A22977@nevyn.them.org> (raw)
In-Reply-To: <15376.60556.71170.277249@krustylu.cygnus.com>
On Fri, Dec 07, 2001 at 11:21:32AM -0500, Elena Zannoni wrote:
> Yes, something like that happened. I am thinking to send a patch to
> restore some sanity to this function. But...
>
> ...actually, I think that if search_symbols on FUNCTION_NAMESPACES is
> equivalent to make_symbol_overload_list(), we could just get rid of
> make_symbol_overload_list() *and* overload_list_add_symbol().
>
> It would be nice to clean this up.
>
> Daniel, does search_symbols produces a correct overload list? At first
> sight it would look so.
Well, I'm not immediately familiar with this code. At first thought,
there might be some complexity because search_symbols takes a regexp,
but that's easily resolvable. More importantly,
make_symbol_overload_list respects scope. So no, the two are not
equivalent.
I found at least one more bug in overload_list_add_symbol (extraneous
realloc calls) while looking this over, though. I also understand
where those loops came from, more or less; see make_completion_list.
This function (and its comments) need some housecleaning.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-07 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 13:38 Andrew Cagney
2001-12-06 14:23 ` Elena Zannoni
2001-12-07 8:15 ` Elena Zannoni
2001-12-07 9:30 ` Daniel Jacobowitz [this message]
2001-12-07 10:03 ` Elena Zannoni
2001-12-07 10:11 ` Daniel Jacobowitz
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=20011207122951.A22977@nevyn.them.org \
--to=drow@mvista.com \
--cc=ezannoni@cygnus.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