public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12188] python gdb.parameter("endian") is ""
Date: Fri, 04 Feb 2011 20:48:00 -0000	[thread overview]
Message-ID: <bug-12188-4717-ap95Ax6LH7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12188-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12188

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2011-02-04 20:48:03 UTC ---
I think the problem is that there is no generic way
to retrieve an "auto" parameter's current value in gdb.
The C code usually just uses the appropriate logic at the
appropriate point, and the show functions are all hard-coded
too.  One clean solution would be to add another method to
the set/show classes.

-- 
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.


  reply	other threads:[~2011-02-04 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 20:14 [Bug python/12188] New: " dje at google dot com
2011-02-04 20:48 ` tromey at redhat dot com [this message]
2022-01-04 16:16 ` [Bug python/12188] " tromey at sourceware dot org
2022-01-26 14:07 ` cvs-commit at gcc dot gnu.org
2024-01-14 14:48 ` ssbssa at sourceware dot org
2024-01-14 16:55 ` 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-12188-4717-ap95Ax6LH7@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: link
Be 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).