public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/14639] New: gdb.parameter doesn't flag ambiguous parameter spellings Date: Thu, 27 Sep 2012 23:13:00 -0000 [thread overview] Message-ID: <bug-14639-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14639 Bug #: 14639 Summary: gdb.parameter doesn't flag ambiguous parameter spellings Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: python AssignedTo: unassigned@sourceware.org ReportedBy: dje@google.com Classification: Unclassified GNU gdb (GDB) 7.5.50.20120927-cvs Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. (gdb) py import gdb (gdb) set print sym on Ambiguous set print command "sym on": symbol, symbol-filename. (gdb) py print gdb.parameter("print sym") False (gdb) Code that needs to work with multiple gdb versions should be able to rely on gdb.parameter raising an exception if setting that parameter is an error. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-09-27 23:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-27 23:13 dje at google dot com [this message] 2023-12-15 18:40 ` [Bug python/14639] " ssbssa at sourceware dot org 2023-12-16 0:22 ` tromey at sourceware dot org 2024-02-07 19:01 ` cvs-commit at gcc dot gnu.org 2024-02-07 19:02 ` ssbssa 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-14639-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).