public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug testsuite/30403] New: [gdb/testsuite] -wrap no longer in sync with gdb_test Date: Sat, 29 Apr 2023 08:05:59 +0000 [thread overview] Message-ID: <bug-30403-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30403 Bug ID: 30403 Summary: [gdb/testsuite] -wrap no longer in sync with gdb_test Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: testsuite Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- The semantics of -wrap is defined as doing what gdb_test does: ... # In EXPECT_ARGUMENTS we can use a -wrap pattern flag, that wraps the regexp # pattern as gdb_test wraps its message argument. # This allows us to rewrite: # gdb_test <command> <pattern> <message> # into: # gdb_test_multiple <command> <message> { # -re -wrap <pattern> { # pass $gdb_test_name # } # } ... There are recent changes in gdb_test semantics, but -wrap was not updated: ... if { $wrap_pattern } { # Wrap subst_item as is done for the gdb_test PATTERN argument. lappend $current_list \ "\[\r\n\]*(?:$subst_item)\[\r\n\]+$prompt_regexp" set wrap_pattern 0 } else { ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-04-29 8:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-29 8:05 vries at gcc dot gnu.org [this message] 2023-04-29 8:06 ` [Bug testsuite/30403] " vries at gcc dot gnu.org 2023-05-04 6:44 ` vries at gcc dot gnu.org 2023-05-05 16:59 ` cvs-commit at gcc dot gnu.org 2023-05-23 5:34 ` vries at gcc dot gnu.org
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=bug-30403-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).