Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Vrany <jan.vrany@labware.com>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan.vrany@labware.com>
Subject: [PATCH 2/2] db/testsuite: fix test build-id-no-debug-warning.exp with -readnow
Date: Tue, 24 Feb 2026 11:15:12 +0000	[thread overview]
Message-ID: <20260224111512.62343-2-jan.vrany@labware.com> (raw)
In-Reply-To: <20260224111512.62343-1-jan.vrany@labware.com>

Test build-id-no-debug-warning.exp fails when using -readnow. This is
because in that case GDB outputs "Expanding full symbols from..." after
"Reading symbols from ...".

Fix this by updating the test.
---
 gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp b/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp
index cfd1a275d89..4fabc9931b4 100644
--- a/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp
+++ b/gdb/testsuite/gdb.debuginfod/build-id-no-debug-warning.exp
@@ -82,7 +82,7 @@ set debug_file_re [string_to_regexp $build_id_debug_file]
 gdb_test "file ${build_id_debug_file}" \
     [multi_line \
 	 "Reading symbols from $debug_file_re\\.\\.\\." \
-	 "warning: \"$debug_file_re\": separate debug info file has no debug info" \
+	 "warning: \"$debug_file_re\": separate debug info file has no debug info(?:\r\nExpanding full symbols from \[^\r\n\]+)*" \
 	 "\\(No debugging symbols found in \[^\r\n\]+\\)"] \
     "load test file, expect a warning"
 
@@ -101,7 +101,7 @@ with_test_prefix "check styling" {
 	gdb_test "file ${build_id_debug_file}" \
 	    [multi_line \
 		 "Reading symbols from $debug_file_re\\.\\.\\." \
-		 "warning: \"$debug_file_re\": separate debug info file has no debug info" \
+		 "warning: \"$debug_file_re\": separate debug info file has no debug info(?:\r\nExpanding full symbols from \[^\r\n\]+)*" \
 		 "\\(No debugging symbols found in \[^\r\n\]+\\)"] \
 	    "load test file, expect a warning"
     }
-- 
2.51.0


  reply	other threads:[~2026-02-24 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 11:15 [PATCH 1/2] gdb/testsuite: fix test crc_mismatch.exp " Jan Vrany
2026-02-24 11:15 ` Jan Vrany [this message]
2026-02-24 15:20   ` [PATCH 2/2] db/testsuite: fix test build-id-no-debug-warning.exp " Tom Tromey
2026-02-24 15:20 ` [PATCH 1/2] gdb/testsuite: fix test crc_mismatch.exp " Tom Tromey

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=20260224111512.62343-2-jan.vrany@labware.com \
    --to=jan.vrany@labware.com \
    --cc=gdb-patches@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: link
Be 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