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 python/31425] New: [gdb/python, 3.12] FAIL: gdb.python/py-block.exp: check nonexistent variable Date: Wed, 28 Feb 2024 09:18:35 +0000 [thread overview] Message-ID: <bug-31425-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31425 Bug ID: 31425 Summary: [gdb/python, 3.12] FAIL: gdb.python/py-block.exp: check nonexistent variable Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: python Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- On aarch64-linux, with python 3.12. Before commit a207f6b3a38 ("Rewrite "python" command exception handling"), we had: ... (gdb) python print (block['nonexistent'])^M Traceback (most recent call last):^M File "<string>", line 1, in <module>^M KeyError: 'nonexistent'^M Error while executing Python code.^M (gdb) PASS: gdb.python/py-block.exp: check nonexistent variable ... but now we have: ... (gdb) python print (block['nonexistent'])^M Python Exception <class 'KeyError'>: 'nonexistent'^M Error occurred in Python: 'nonexistent'^M (gdb) FAIL: gdb.python/py-block.exp: check nonexistent variable ... The change in the test-case is: ... -gdb_test "python print (block\['nonexistent'\])" ".*KeyError: 'nonexistent'.*" \ +gdb_test "python print (block\['nonexistent'\])" ".*KeyError.*: nonexistent.*" \ "check nonexistent variable" ... which drops the single quotes around the nonexistent string. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-28 9:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 9:18 vries at gcc dot gnu.org [this message] 2024-02-28 9:27 ` [Bug python/31425] " vries at gcc dot gnu.org 2024-02-28 9:39 ` vries at gcc dot gnu.org 2024-02-28 9:58 ` vries at gcc dot gnu.org 2024-02-28 10:05 ` vries at gcc dot gnu.org 2024-02-28 11:01 ` vries at gcc dot gnu.org 2024-02-28 15:00 ` tromey at sourceware dot org 2024-02-28 20:01 ` vries at gcc dot gnu.org 2024-03-04 16:05 ` vries at gcc dot gnu.org 2024-03-09 15:15 ` 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-31425-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).