Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com,
	Elena Zannoni <ezannoni@redhat.com>, Jim Blandy <jimb@redhat.com>
Subject: Re: [rfa] delete lookup_symbol_aux_minsyms
Date: Sat, 22 Feb 2003 21:23:00 -0000	[thread overview]
Message-ID: <20030222205011.GA25494@nevyn.them.org> (raw)
In-Reply-To: <ro1el605bwf.fsf@jackfruit.Stanford.EDU>

On Sat, Feb 22, 2003 at 11:54:40AM -0800, David Carlton wrote:
> So what's the conclusion?  Performance considerations don't seem to
> give a clear answer.  So we should go with whatever's cleanest.  My
> recommendation:
> 
> * Delete the 'else' clause: it might cause correctness problems.
> 
> * Comment out the remaining part of lookup_symbol_aux_minsyms: if
>   somebody comes up with a situation where we spend lots of time
>   searching for functions that aren't in a loaded symtab, we can
>   consider uncommenting it and adding it back in.

I'm pretty sure the answer is "none at all" based on skimming the code,
but what affect does removing lookup_symbol_aux_minsyms have when
looking for something which turns out not to have debugging info? 
lookup_symbol would fail, so it doesn't matter - is that right?

I don't know if I like this comment-out-part-delete-part business; if
we don't want the function, let's kill it.


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-22 21:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-22 19:54 David Carlton
2003-02-22 21:23 ` Daniel Jacobowitz [this message]
2003-02-24 18:04   ` David Carlton
2003-02-24 18:17     ` Elena Zannoni
2003-02-24 18:37       ` David Carlton
2003-02-24 18:52         ` Elena Zannoni
2003-02-24 23:43           ` 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=20030222205011.GA25494@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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