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: Thu, 27 Jun 2013 20:43:00 -0000	[thread overview]
Message-ID: <874ncjmgkl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1372043502-4618-1-git-send-email-yao@codesourcery.com> (Yao Qi's	message of "Mon, 24 Jun 2013 11:11:42 +0800")

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

Yao> The rationale of this patch is to fix up the type of minimal symbol to
Yao> "mst_solib_trampoline" when reading the file if the minimal symbol is
Yao> a dll trampoline.  We find that there is always a symbol "_impl_foo"
Yao> coexists with dll trampoline "foo" in the current minimal symbols red
Yao> in.  Our approach is to collect all minimal symbols which name has
Yao> prefix "_imp_", remove the prefix, and find minimal symbols.  If
Yao> found, it is a dll trampoline.

This seems reasonable to me.

Yao> +	 minimal symbols just red in by matching the minimal symbol name

s/red/read/

Yao> +	  char *buffer = xstrdup (SYMBOL_LINKAGE_NAME (msym_dll));

I don't think you need to copy the name here.

Yao> +/* Look for the minimal symbol which name is NAME.  Return NULL if not

"whose name".

I think this comment needs to be expanded (and moved, see below).
It should at least mention that this only searches minsyms that are
currently being constructed.  Otherwise it isn't clear why you would use
this function as opposed to lookup_minimal_symbol_and_objfile.

Yao> +struct minimal_symbol* prim_find_minimal_symbol (const char *name);

The comment should go here, the way it does for other functions in the
minsyms module.

Also, the first "*" is in the wrong place.

thanks,
Tom


  reply	other threads:[~2013-06-27 20:42 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 [this message]
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
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=874ncjmgkl.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