public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Fix gdb.dwarf2/debug-names.exp Date: Tue, 9 Aug 2022 13:12:08 +0000 (GMT) [thread overview] Message-ID: <20220809131208.C3F7D385AC2F@sourceware.org> (raw) 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>"
reply other threads:[~2022-08-09 13:12 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220809131208.C3F7D385AC2F@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).