This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 6 Jul 2016 10:11:22 +0200
- Subject: Re: [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors
- Authentication-results: sourceware.org; auth=none
- References: <20160705145454.GA26978@host1.jankratochvil.net> <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