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/29920] [gdb/testsuite] FAIL: gdb.cp/step-and-next-inline.exp: no_header: next step 1
Date: Tue, 20 Dec 2022 09:48:18 +0000	[thread overview]
Message-ID: <bug-29920-4717-f3gvFYvTLc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29920-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29920

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|gdb                         |testsuite
            Summary|[gdb] FAIL:                 |[gdb/testsuite] FAIL:
                   |gdb.cp/step-and-next-inline |gdb.cp/step-and-next-inline
                   |.exp: no_header: next step  |.exp: no_header: next step
                   |1                           |1

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Fix:
...
diff --git a/gdb/testsuite/gdb.cp/step-and-next-inline.exp
b/gdb/testsuite/gdb.cp/step-and-next-inline.exp
index 8b2ad2766bc..36fac239e2f 100644
--- a/gdb/testsuite/gdb.cp/step-and-next-inline.exp
+++ b/gdb/testsuite/gdb.cp/step-and-next-inline.exp
@@ -60,7 +60,16 @@ proc do_test { use_header } {
     }

     gdb_test "bt" "\\s*\\#0\\s+main.*" "in main"
-    gdb_test "step" ".*" "step into get_alias_set"
+    set line1 {\t\{}
+    set line2 {\t  if \(t != NULL}
+    gdb_test_multiple "step" "step into get_alias_set" {
+       -re -wrap $line1 {
+           gdb_test "next" $line2 $gdb_test_name
+       }
+       -re -wrap $line2 {
+           pass $gdb_test_name
+       }
+    }
     gdb_test "bt" "\\s*\\#0\\s+get_alias_set\[^\r\]*${srcfile}:.*" \
        "not in inline 1"

...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-12-20  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20  8:58 [Bug gdb/29920] New: [gdb] " vries at gcc dot gnu.org
2022-12-20  9:14 ` [Bug gdb/29920] " vries at gcc dot gnu.org
2022-12-20  9:48 ` vries at gcc dot gnu.org [this message]
2022-12-21  8:07 ` [Bug testsuite/29920] [gdb/testsuite] " vries at gcc dot gnu.org
2022-12-23  8:15 ` vries at gcc dot gnu.org
2022-12-30 13:00 ` cvs-commit at gcc dot gnu.org
2022-12-30 13:02 ` 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-29920-4717-f3gvFYvTLc@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).