After this commit:
b744723f57 -- Show line numbers in output for "info var/func/type"
the test cases dbx.exp and info-fun.exp yield new FAILs because two
regular expressions have not been adjusted to the changed output yet.
This is fixed.
gdb/testsuite/ChangeLog:
* gdb.base/dbx.exp (test_whereis): Adjust regexp to added line
number information in output of "whereis" command.
* gdb.base/info-fun.exp: Likewise, for "info fun" command.
+2018-04-16 Andreas Arnez <arnez@linux.vnet.ibm.com>
+
+ * gdb.base/dbx.exp (test_whereis): Adjust regexp to added line
+ number information in output of "whereis" command.
+ * gdb.base/info-fun.exp: Likewise, for "info fun" command.
+
2018-04-13 Andreas Arnez <arnez@linux.vnet.ibm.com>
* gdb.ada/info_types.exp: Adjust expected output to the line
#test_whereis
#
proc test_whereis { } {
- gdb_test "whereis my_list" "All variables matching regular expression \"my_list\":\r\n\r\nFile.*average\.c:\r\nstatic int my_list\\\[10\\\];"
+ gdb_test "whereis my_list" "All variables matching regular expression \"my_list\":\r\n\r\nFile.*average\.c:\r\n.*\tstatic int my_list\\\[10\\\];"
}
#
set match_str {All functions matching regular expression "foo":[\r\n]*}
if { "$libsepdebug" != "NO" } {
append match_str {File .*/info-fun-solib[.]c:[\r\n]*}
- append match_str {int foo\(void\);[\r\n]*}
+ append match_str {\d+:\tint foo\(void\);[\r\n]*}
}
append match_str {Non-debugging symbols:[\r\n]*}
# Note: Targets like {m68k,ppc64,s390x}-linux also have, e.g.,