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/30185] FAIL: gdb.python/py-record-btrace.exp: function call: python print(c == c.next.prev)
Date: Wed, 01 Mar 2023 11:08:25 +0000	[thread overview]
Message-ID: <bug-30185-4717-USw0mwGBvM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30185-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
If this the same root cause as the existing xfail, we can detect it using:
...
diff --git a/gdb/testsuite/gdb.python/py-record-btrace.exp
b/gdb/testsuite/gdb.p
ython/py-record-btrace.exp
index 703db0ce8e1..f62316b7b1c 100644
--- a/gdb/testsuite/gdb.python/py-record-btrace.exp
+++ b/gdb/testsuite/gdb.python/py-record-btrace.exp
@@ -101,6 +101,23 @@ with_test_prefix "prepare record" {
        return
     }

+    gdb_test_multiple "python print(len(insn))" "" {
+       -re -wrap "100" {
+           pass $gdb_test_name
+       }
+       -re -wrap "" {
+           if { $have_xfail } {
+               xfail $gdb_test_name
+               set got_xfail 1
+           } else {
+               fail $gdb_test_name
+           }
+       }
+    }
+    if { $got_xfail } {
+       return
+    }
+
     gdb_test_no_output "python call = r.function_call_history"
     gdb_test_no_output "python i = insn\[0\]"
     gdb_test_no_output "python c = call\[0\]"
@@ -138,7 +155,6 @@ with_test_prefix "function call" {
 }

 with_test_prefix "list" {
-    gdb_test "python print(len(insn))" "100"
     gdb_test "python print(len(insn\[23:65\]))" "42"
     gdb_test "python print(insn\[17:\]\[2\].number)" "20"
     gdb_test "python print(i in insn)" "True"
...

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

  parent reply	other threads:[~2023-03-01 11:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 10:57 [Bug testsuite/30185] New: FAIL: gdb.python/py-record-btrace.exp: function call: pyth\ on " vries at gcc dot gnu.org
2023-03-01 10:57 ` [Bug testsuite/30185] FAIL: gdb.python/py-record-btrace.exp: function call: python " vries at gcc dot gnu.org
2023-03-01 10:57 ` vries at gcc dot gnu.org
2023-03-01 10:58 ` vries at gcc dot gnu.org
2023-03-01 11:08 ` vries at gcc dot gnu.org [this message]
2023-03-01 11:29 ` markus.t.metzger at intel dot com
2023-03-01 11:44 ` vries at gcc dot gnu.org
2023-03-01 12:43 ` cvs-commit at gcc dot gnu.org
2023-03-01 12:44 ` 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-30185-4717-USw0mwGBvM@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).