public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "chrisj at rtems dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11380] New: print formats (/FMT) do not invoke Python pretty printers
Date: Mon, 15 Mar 2010 22:49:00 -0000 [thread overview]
Message-ID: <20100315224909.11380.chrisj@rtems.org> (raw)
If a /FMT is used with the print command a type's pretty printer is not invoked.
For example a pretty printer to print an RTEMS Object ID (an unsigned long)
produces:
(gdb) p /f the_semaphore->Object.id
$10 = to_string = {
id = 436273170,
node = 1,
api = classic,
class = semaphores,
index = 18
}
and with a /FMT option added:
(gdb) p /c the_semaphore->Object.id
$15 = 18 '\022'
(gdb) p /f the_semaphore->Object.id
$16 = 2.66766316e-23
(gdb) p /u the_semaphore->Object.id
$17 = 436273170
(gdb) p /t the_semaphore->Object.id
$18 = 11010000000010000000000010010
It would be nice if the pretty printer followed the requested output where a
printer is creating a struct type output (display hint 'struct').
--
Summary: print formats (/FMT) do not invoke Python pretty
printers
Product: gdb
Version: 7.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned at sourceware dot org
ReportedBy: chrisj at rtems dot org
CC: gdb-prs at sourceware dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=11380
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-03-15 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 22:49 chrisj at rtems dot org [this message]
2010-04-19 7:25 ` [Bug python/11380] " pmuldoon at redhat dot com
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=20100315224909.11380.chrisj@rtems.org \
--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).