Skip to content

Commit

Permalink
[gdb/testsuite] Fix gdb.dwarf2/debug-names.exp
Browse files Browse the repository at this point in the history
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.
vries committed Aug 9, 2022
1 parent 8cf61a3 commit a8a8829
Showing 1 changed file with 4 additions and 7 deletions.
11 changes: 4 additions & 7 deletions gdb/testsuite/gdb.dwarf2/debug-names.exp
Original file line number Diff line number Diff line change
@@ -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>"

0 comments on commit a8a8829

Please sign in to comment.