public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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 12:43:58 +0000 [thread overview]
Message-ID: <bug-30185-4717-n3jHvMc9e1@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 #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2c29b1ed19711fa2a16558015e5a6b46a09aefeb
commit 2c29b1ed19711fa2a16558015e5a6b46a09aefeb
Author: Tom de Vries <tdevries@suse.de>
Date: Wed Mar 1 13:44:04 2023 +0100
[gdb/testsuite] Add another xfail case in gdb.python/py-record-btrace.exp
I ran into:
...
(gdb) PASS: gdb.python/py-record-btrace.exp: function call: \
python print(c.prev)
python print(c == c.next.prev)^M
Traceback (most recent call last):^M
File "<string>", line 1, in <module>^M
AttributeError: 'NoneType' object has no attribute 'prev'^M
Error while executing Python code.^M
(gdb) FAIL: gdb.python/py-record-btrace.exp: function call: \
python print(c == c.next.prev)
...
due to having only 4 insn instead of 100:
...
python print(len(insn))^M
4^M
...
This could be caused by the same hw bug as we already have an xfail for, so
expand the xfail matching.
Tested on x86_64-linux.
PR testsuite/30185
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30185
Approved-By: Markus T. Metzger <markus.t.metzger@intel.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-01 12:43 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
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 [this message]
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-n3jHvMc9e1@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).