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/12188] New: python gdb.parameter("endian") is ""
Date: Wed, 03 Nov 2010 20:14:00 -0000	[thread overview]
Message-ID: <bug-12188-4717@http.sourceware.org/bugzilla/> (raw)

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

           Summary: python gdb.parameter("endian") is ""
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dje@google.com


Conversion of gdb parameters to python is not always correct.

Here's an example:

bash$ gdb
[...]
(gdb) show endian
The target endianness is set automatically (currently little endian)
(gdb) python print gdb.parameter("endian")

(gdb)

i.e. the value is ""

Explicitly setting the value to "auto" then yields a better result.

(gdb) set endian auto
The target endianness is set automatically (currently little endian)
(gdb) python print gdb.parameter("endian")
auto

Plus it would be useful to see the actual endianness from python, instead of
having to watch for and handle "auto".

-- 
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:[~2010-11-03 17:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 20:14 dje at google dot com [this message]
2011-02-04 20:48 ` [Bug python/12188] " tromey at redhat dot com
2022-01-04 16:16 ` 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@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).