Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors
Date: Wed, 06 Jul 2016 08:11:00 -0000	[thread overview]
Message-ID: <20160706081122.GA19754@host1.jankratochvil.net> (raw)
In-Reply-To: <CAH=s-PMKOAYhx+62K_YmBPqcqOm0ex6ijftrWhsf1nJNM7wY6w@mail.gmail.com>

On Wed, 06 Jul 2016 09:51:15 +0200, Yao Qi wrote:
> If we hack gdb.dwarf2/dw2-bad-mips-linkage-name.exp like this,  "f" -> ".f",
> and "g" -> ".g",

OK, I didn't realize that the ".dotted" synthetic symbols can be used even in
as/ld, not just inside GDB.


> The right fix would be teaching proc gdb_target_symbol to add
> prefix "." to symbol if target is powerpc64 and abi is ELFv1, in which function
> descriptor is used.

Now the question is how to detect that.  I used "powerpc64-*linux*" target
match in my patch but I guess that is not right.  Maybe it could compile first
something and check if ".somesymbol" exists.


Thanks,
Jan


  reply	other threads:[~2016-07-06  8:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05 14:55 Jan Kratochvil
2016-07-06  7:51 ` Yao Qi
2016-07-06  8:11   ` Jan Kratochvil [this message]
2016-07-06 19:35     ` [testsuite patchv2] [ppc64] gdb_target_symbol fix for function descriptors [Re: [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors] Jan Kratochvil
2016-07-12 12:56       ` Yao Qi
2016-07-12 13:22         ` [testsuite patchv2] [ppc64] gdb_target_symbol fix for function descriptors [Re: [testsuite patch] [ppc64] +kfail: gdb_target Ulrich Weigand
2016-07-13  8:54           ` [testsuite patchv3] " Jan Kratochvil
2016-07-13 11:52             ` Ulrich Weigand
2016-07-13 12:02               ` [commit] " Jan Kratochvil

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=20160706081122.GA19754@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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