Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix up msymbol type of dll trampoline to mst_solib_trampoline
Date: Wed, 10 Jul 2013 16:56:00 -0000	[thread overview]
Message-ID: <87vc4igxq6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <51D36FB3.4070006@codesourcery.com> (Yao Qi's message of "Wed, 3	Jul 2013 08:26:27 +0800")

>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:

Yao> That is, after the hash table of minsyms of OBJFILE is built up, we
Yao> can iterate all minsyms, if symbol is _imp_x, look up x in the hash
Yao> table.  If found, modify the found's type.

Yao> +      for (i = objfile->minimal_symbol_count; i > 0; i--)

This should use ALL_OBJFILE_MSYMBOLS.

I'm mildly concerned that this exposes an implementation detail of the
minsym storage -- namely, it assumes that it is ok to modify a minsym
after the minsym is installed.

This approach would also block constification of the minsym API.

Neither of these seem like blocking considerations though.  Presumably
bugs arising from the first would be caught in testing; and for the
second, casting away const would be obviously ok.

So, ok with the ALL_OBJFILE_MSYMBOLS change.

Tom


  parent reply	other threads:[~2013-07-10 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  4:24 Yao Qi
2013-06-27 20:43 ` Tom Tromey
2013-06-28  7:37   ` Yao Qi
2013-06-28 15:58     ` Tom Tromey
2013-07-03  0:26       ` Yao Qi
2013-07-05  8:44         ` asmwarrior
2013-07-05 12:22           ` Yao Qi
2013-07-05 14:30             ` Eli Zaretskii
2013-07-06  7:21               ` Yao Qi
2013-07-06  7:41                 ` Eli Zaretskii
2013-07-06  8:20                   ` asmwarrior
2013-07-10  6:21         ` Yao Qi
2013-07-10 16:56         ` Tom Tromey [this message]
2013-07-18  2:09           ` Yao Qi
2013-07-18  3:26             ` Yao Qi

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=87vc4igxq6.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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