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 python/29217] gdb.set_parameter doesn't accept a bool where gdb.parameter returns one Date: Fri, 08 Jul 2022 20:07:31 +0000 [thread overview] Message-ID: <bug-29217-4717-sZLUGq1GDG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29217-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29217 --- 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=fa17a6814113ac22d8059d61514aa2c6e29b0aae commit fa17a6814113ac22d8059d61514aa2c6e29b0aae Author: Tom Tromey <tom@tromey.com> Date: Sun Jun 12 11:36:08 2022 -0600 Handle bool specially in gdb.set_parameter PR python/29217 points out that gdb.parameter will return bool values, but gdb.set_parameter will not properly accept them. This patch fixes the problem by adding a special case to set_parameter. I looked at a fix involving rewriting set_parameter in C++. However, this one is simpler. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29217 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-08 20:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-01 12:11 [Bug python/29217] New: " plasmahh at gmx dot net 2022-06-05 23:07 ` [Bug python/29217] " tromey at sourceware dot org 2022-07-08 20:07 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-08 20:09 ` tromey at sourceware dot org 2022-10-21 7:56 ` cvs-commit 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-29217-4717-sZLUGq1GDG@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).