public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug guile/17203] It should be an error to register a pre-existing parameter. Date: Mon, 28 Jul 2014 14:50:00 -0000 [thread overview] Message-ID: <bug-17203-4717-GXcon12NGn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17203-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17203 --- Comment #4 from Doug Evans <xdje42 at gmail dot com> --- On a related topic, One thing I'd like to add is the ability to export native gdb parameters to Scheme. One reason is I'd like to write a function that executes a gdb command with a parameter temporarily set to a specified value. In order to easily do that, i.e., without having to have a lot of parameter-specific code, I want to be able to read and write parameters from Scheme and not using gdb set/show commands. Implementing this will involve a bit of work for parameters that post-process writes. The point of noting this here is that in this case we're not registering a new parameter (using the parlance of "register-parameter!"), just exporting to Scheme an existing one. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-07-28 14:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-27 4:38 [Bug guile/17203] New: " xdje42 at gmail dot com 2014-07-28 13:30 ` [Bug guile/17203] " brobecker at gnat dot com 2014-07-28 14:30 ` xdje42 at gmail dot com 2014-07-28 14:35 ` brobecker at adacore dot com 2014-07-28 14:50 ` xdje42 at gmail dot com [this message] 2014-07-29 2:28 ` cvs-commit at gcc dot gnu.org 2024-01-19 12:27 ` 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-17203-4717-GXcon12NGn@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).