public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "avi at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/13907] New: RFE: Resolve static pointers in pretty printer
Date: Tue, 27 Mar 2012 13:38:00 -0000	[thread overview]
Message-ID: <bug-13907-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13907
           Summary: RFE: Resolve static pointers in pretty printer
           Product: gdb
           Version: 7.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: exp
        AssignedTo: unassigned@sourceware.org
        ReportedBy: avi@redhat.com
    Classification: Unclassified


When gdb prints out a function pointer, it looks it up in the symbol table and
prints the function name:

  $5 = {read = 0x55555567f85f <pic_ioport_read>, ...

However, it doesn't do the same for data pointers:

  $3 = {ops = 0x555555b6ba60, ...
  (gdb) p &pic_base_ioport_ops 
  $6 = (const MemoryRegionOps *) 0x555555b6ba60

It would be nice if $3 read as

  $3 = {ops = 0x555555b6ba60 <&pic_base_ioport_ops>, ...

-- 
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:[~2012-03-27 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 13:38 avi at redhat dot com [this message]
2012-03-30 14:50 ` [Bug exp/13907] " tromey at redhat dot com
2012-05-18 15:32 ` cvs-commit at gcc dot gnu.org
2012-05-18 15:33 ` tromey 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=bug-13907-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).