From a8a882968a6cd3bfe64d789b6e914521c74498c2 Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Tue, 9 Aug 2022 15:12:05 +0200 Subject: [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. --- gdb/testsuite/gdb.dwarf2/debug-names.exp | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) (limited to 'gdb') 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 .*" "break _start expanded symtab" +# Verify that _start is found in the debuginfo, rather than in the minimal +# symbols, which would result instead in: +# $1 = {} $hex <_start> +gdb_test "print _start" " = {void \\(\\)} $hex <_start>" -- cgit v1.1