aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2022-08-09 15:12:05 +0200
committerTom de Vries <tdevries@suse.de>2022-08-09 15:12:05 +0200
commita8a882968a6cd3bfe64d789b6e914521c74498c2 (patch)
tree37f674d50269b719266f01254f3e939dd3bf38a7 /gdb
parent8cf61a33bba791c38e1b2f6cf2f276d052a1f17e (diff)
downloadfsf-binutils-gdb-a8a882968a6cd3bfe64d789b6e914521c74498c2.zip
fsf-binutils-gdb-a8a882968a6cd3bfe64d789b6e914521c74498c2.tar.gz
fsf-binutils-gdb-a8a882968a6cd3bfe64d789b6e914521c74498c2.tar.bz2
[gdb/testsuite] Fix gdb.dwarf2/debug-names.exp
When running test-case gdb.dwarf2/debug-names.exp on openSUSE Tumbleweed, I run into: ... (gdb) maint info symtabs^M ... ERROR: internal buffer is full. UNRESOLVED: gdb.dwarf2/debug-names.exp: break _start expanded symtab ... Fix this by simplifying the test-case to print _start rather running to it. Tested on x86_64-linux.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/testsuite/gdb.dwarf2/debug-names.exp11
1 files changed, 4 insertions, 7 deletions
diff --git a/gdb/testsuite/gdb.dwarf2/debug-names.exp b/gdb/testsuite/gdb.dwarf2/debug-names.exp
index 0af5a93..e625c1f 100644
--- a/gdb/testsuite/gdb.dwarf2/debug-names.exp
+++ b/gdb/testsuite/gdb.dwarf2/debug-names.exp
@@ -70,10 +70,7 @@ gdb_assert { [string equal $index "debug_names"] } ".debug_names used"
# Verify that initially no symtab is expanded.
gdb_test_no_output "maint info symtabs"
-if ![runto _start] {
- return -1
-}
-
-# Verify that breaking on _start actually expanded a symtab, rather than
-# falling back on minimal symbols.
-gdb_test "maint info symtabs" "name <unknown>.*" "break _start expanded symtab"
+# Verify that _start is found in the debuginfo, rather than in the minimal
+# symbols, which would result instead in:
+# $1 = {<text variable, no debug info>} $hex <_start>
+gdb_test "print _start" " = {void \\(\\)} $hex <_start>"