From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Kevin Buettner <kevinb@redhat.com>
Subject: [testsuite patchv2] [ppc64] gdb_target_symbol fix for function descriptors [Re: [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors]
Date: Wed, 06 Jul 2016 19:35:00 -0000 [thread overview]
Message-ID: <20160706193508.GA2313@host1.jankratochvil.net> (raw)
In-Reply-To: <20160706081122.GA19754@host1.jankratochvil.net>
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
On Wed, 06 Jul 2016 10:11:22 +0200, Jan Kratochvil wrote:
> 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.
Implemented the compile test.
It works for me on RHEL-7.2 ppc64 and on Fedora 24 x86_64.
OK for check-in?
I see gdb_target_symbol_prefix is by Kevin so Ccing him if he sees it OK even
on those platforms.
Thanks,
Jan
[-- Attachment #2: 1 --]
[-- Type: text/plain, Size: 1777 bytes --]
gdb/testsuite/ChangeLog
2016-07-06 Jan Kratochvil <jan.kratochvil@redhat.com>
* lib/gdb.exp (gdb_target_code_symbol_prefix): New.
(gdb_target_symbol): Call it.
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index b7b8fad..7e64edc 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5690,11 +5690,48 @@ gdb_caching_proc gdb_target_symbol_prefix {
return $prefix
}
+# gdb_target_code_symbol_prefix compiles a test program and tries to use
+# '.' prefix at a code symbol to test if there are function descriptors.
+# gdb_target_symbol_prefix is not expected to be needed on such targets.
+
+gdb_caching_proc gdb_target_code_symbol_prefix {
+ # Set up and compile a simple test program...
+ set srcc [standard_temp_file main[pid].c]
+ set srcs [standard_temp_file main[pid].s]
+ set exe [standard_temp_file main[pid].x]
+
+ gdb_produce_source $srcc {
+ int main() {
+ return 0;
+ }
+ }
+ gdb_produce_source $srcs {
+ .8byte .main
+ }
+
+ verbose "compiling testfile $srcc $srcs" 2
+ set compile_flags {nodebug nowarnings quiet}
+ set lines [gdb_compile "$srcc $srcs" $exe executable $compile_flags]
+
+ set prefix ""
+
+ if [string match "" $lines] then {
+ verbose "gdb_target_code_symbol_prefix: returning \".\" prefix" 2
+ set prefix "."
+ }
+
+ file delete $srcc
+ file delete $srcs
+ file delete $exe
+
+ return $prefix
+}
+
# gdb_target_symbol returns the provided symbol with the correct prefix
-# prepended. (See gdb_target_symbol_prefix, above.)
+# prepended.
proc gdb_target_symbol { symbol } {
- set prefix [gdb_target_symbol_prefix]
+ set prefix [gdb_target_symbol_prefix][gdb_target_code_symbol_prefix]
return "${prefix}${symbol}"
}
next prev parent reply other threads:[~2016-07-06 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 14:55 [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors Jan Kratochvil
2016-07-06 7:51 ` Yao Qi
2016-07-06 8:11 ` Jan Kratochvil
2016-07-06 19:35 ` Jan Kratochvil [this message]
2016-07-12 12:56 ` [testsuite patchv2] [ppc64] gdb_target_symbol fix for function descriptors [Re: [testsuite patch] [ppc64] +kfail: gdb_target_symbol does not support function descriptors] 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=20160706193508.GA2313@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--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