Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: gdb-patches@sources.redhat.com
Cc: Elena Zannoni <ezannoni@redhat.com>, Jim Blandy <jimb@redhat.com>
Subject: Re: [patch] add linkage_name argument to lookup_partial_symbol
Date: Mon, 03 Mar 2003 20:04:00 -0000	[thread overview]
Message-ID: <ro14r6kgqt9.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro18yvwgrfl.fsf@jackfruit.Stanford.EDU>

On 03 Mar 2003 11:50:54 -0800, David Carlton <carlton@math.Stanford.EDU> said:

> Currently, lookup_partial_symbol only matches on natural names, not on
> linkage names.  This can be a problem when it's called from
> lookup_symbol_aux_psymtabs: that functions cares about the linkage
> name of the symbol in addition to its natural name.  So the wrong
> partial symtab could be found, leading to a "name found in psymtab but
> not in symtab" error.

I should also add another observation: after this patch goes in, every
use of SYMBOL_MATCHES_NATURAL_NAME in symtab.c will be paired with a
check on linkage names.  This suggests that perhaps we should replace
SYMBOL_MATCHES_NATURAL_NAME by a macro SYMBOL_MATCHES_NAMES that
accepts a symbol, a linkage name (which might be NULL), and a natural
name.

On the other hand, we still have the uses of
DEPRECATED_SYMBOL_MATCHES_NAME in minsyms.c, and there such a
SYMBOL_MATCHES_NAMES wouldn't be appropriate (though the current
SYMBOL_MATCHES_NATURAL_NAME might be).  So it's not something to do
right now, but it probably is something to keep in mind once minsyms.c
has gotten cleaned up a bit, when we'll have a better idea where this
macro might be used.  (We should probably audit all uses of strcmp_iw
within GDB when doing this.)

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2003-03-03 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-03 20:36 David Carlton
2003-03-03 20:04 ` David Carlton [this message]
2003-03-04 17:06 ` 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=ro14r6kgqt9.fsf@jackfruit.Stanford.EDU \
    --to=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