[binutils-gdb] [gdb/testsuite] Fix gdb.dwarf2/debug-names.exp

[binutils-gdb] [gdb/testsuite] Fix gdb.dwarf2/debug-names.exp

[Tom de Vries]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a8a882968a6cd3bfe64d789b6e914521c74498c2

commit a8a882968a6cd3bfe64d789b6e914521c74498c2
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Aug 9 15:12:05 2022 +0200

    [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.

Diff:
---
 gdb/testsuite/gdb.dwarf2/debug-names.exp | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/gdb/testsuite/gdb.dwarf2/debug-names.exp b/gdb/testsuite/gdb.dwarf2/debug-names.exp
index 0af5a93bea8..e625c1fbb7a 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>"