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 gdb/30253] [gdb] FAIL: gdb.gdb/python-helper.exp: pretty print type->main_type Date: Mon, 20 Mar 2023 17:41:01 +0000 [thread overview] Message-ID: <bug-30253-4717-4B5Ka8yeuW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30253-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30253 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=505ca0bfa52845fb7793b9f2a808c7c5aa4677fd commit 505ca0bfa52845fb7793b9f2a808c7c5aa4677fd Author: Tom Tromey <tromey@adacore.com> Date: Mon Mar 20 10:18:22 2023 -0600 Update python-helper.exp for type allocation changes The type allocation changes introduced a failure in python-helper.exp that I did not notice. The bug is that, with these patches, arch-allocated integer types have a TYPE_SPECIFIC_INT object attached. This patch updates the test to allow this. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30253 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-20 17:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-20 16:04 [Bug gdb/30253] New: " vries at gcc dot gnu.org 2023-03-20 16:12 ` [Bug gdb/30253] " tromey at sourceware dot org 2023-03-20 16:20 ` tromey at sourceware dot org 2023-03-20 17:41 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-20 17:41 ` tromey at sourceware dot 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-30253-4717-4B5Ka8yeuW@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).