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: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] more lookup_symbol_aux_minsyms futzing
Date: Thu, 20 Feb 2003 21:18:00 -0000	[thread overview]
Message-ID: <20030220211642.GA24294@nevyn.them.org> (raw)
In-Reply-To: <ro11y22656m.fsf@jackfruit.Stanford.EDU>

On Thu, Feb 20, 2003 at 12:57:37PM -0800, David Carlton wrote:
> On Thu, 20 Feb 2003 15:08:19 -0500, Elena Zannoni <ezannoni@redhat.com> said:
> 
> > A few comments
> 
> Ack! I was considering this patch to be withdrawn, and I hadn't
> noticed that it got added to GNATS.  Right now, all I'm proposing is
> the search_symbols part of this patch (with a comment added), as in PR
> symtab/1049.  (Incidentally, I'm curious if Daniel considers the patch
> in symtab/1070 to still be active: if so, please review the e-mail
> discussion that Daniel and I had about this.  I actually have more to
> say about that if you're considering approving that patch.)

Yes, I never withdrew it; that's why I forwarded it to GNATS.

> 1) A patch to correct a slight bug that remains in
>    lookup_partial_symbol.  Basically, partial symbols are sorted via
>    strcmp but we want to use strcmp_iw as our matching criterion;
>    strcmp and strcmp_iw aren't _quite_ suitable to be used together in
>    this way.

Should they be sorted via strcmp_iw instead?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-20 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23 10:56 David Carlton
2002-12-24  1:56 ` Jason Molenda
2002-12-24 10:05   ` David Carlton
2002-12-24 16:34     ` Jason Molenda
2003-02-20 20:04 ` Elena Zannoni
2003-02-20 20:57   ` David Carlton
2003-02-20 21:18     ` Daniel Jacobowitz [this message]
2003-02-20 21:35       ` 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=20030220211642.GA24294@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@math.stanford.edu \
    --cc=ezannoni@redhat.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