aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYao Qi <yao@codesourcery.com>2014-06-06 19:16:47 +0800
committerYao Qi <yao@codesourcery.com>2014-06-06 21:43:26 +0800
commitd9a472877066d56b0546af71890bc92eef85df67 (patch)
tree0a8e8375445a13a169c5b9f655ac38302afbca2f
parente5e01dbf8911d62631e5f53c083477442e2f1119 (diff)
downloadgdb-d9a472877066d56b0546af71890bc92eef85df67.zip
gdb-d9a472877066d56b0546af71890bc92eef85df67.tar.gz
gdb-d9a472877066d56b0546af71890bc92eef85df67.tar.bz2
Restrict the pattern in gdb.base/jit.exp
I see the following fail in some thumb multi-lib in arm-none-linux-gnueabi, info function jit_function^M All functions matching regular expression "jit_function":^M ^M Non-debugging symbols:^M 0x00000790 __real_jit_function_XXXX^M 0x0000079c __jit_function_XXXX_from_arm^M 0x0000079c jit_function_0000^M 0x00000790 __real_jit_function_XXXX^M 0x0000079c __jit_function_XXXX_from_arm^M 0x0000079c jit_function_0001^M (gdb) FAIL: gdb.base/jit.exp: one_jit_test-2: info function jit_function the test expects to see only jit_function_0000 and jit_function_0001 one_jit_test 2 "${hex} jit_function_0000\[\r\n\]+${hex} jit_function_0001" Symbols with the prefix "__real_" or suffix "_from_arm" is generated by gcc/ld for arm/thumb interworking. This patch is to restrict the pattern from "jit_function" to "^jit_function", the output becomes expected. gdb/testsuite: 2014-06-06 Yao Qi <yao@codesourcery.com> * gdb.base/jit.exp (one_jit_test): Restrict the pattern from "jit_function" to "^jit_function".
-rw-r--r--gdb/testsuite/ChangeLog5
-rw-r--r--gdb/testsuite/gdb.base/jit.exp2
2 files changed, 6 insertions, 1 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 5484618..c513d08 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,10 @@
2014-06-06 Yao Qi <yao@codesourcery.com>
+ * gdb.base/jit.exp (one_jit_test): Restrict the pattern
+ from "jit_function" to "^jit_function".
+
+2014-06-06 Yao Qi <yao@codesourcery.com>
+
* gdb.base/async.c (foo): Add one statement.
* gdb.base/async.exp: Get the next instruction address and
match the output of "nexti" by instruction address. Match
diff --git a/gdb/testsuite/gdb.base/jit.exp b/gdb/testsuite/gdb.base/jit.exp
index 366c8b3..ca6e6c3 100644
--- a/gdb/testsuite/gdb.base/jit.exp
+++ b/gdb/testsuite/gdb.base/jit.exp
@@ -93,7 +93,7 @@ proc one_jit_test {count match_str} {
gdb_breakpoint [gdb_get_line_number "break here 1"]
gdb_continue_to_breakpoint "break here 1"
- gdb_test "info function jit_function" "$match_str"
+ gdb_test "info function ^jit_function" "$match_str"
# This is just to help debugging when things fail
if {$verbose > 0} {