public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andre dot poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/11777] New: Strange behaviour of gdb.Type.fields
Date: Thu, 01 Jul 2010 07:20:00 -0000	[thread overview]
Message-ID: <20100701072012.11777.andre.poenitz@nokia.com> (raw)

I sometimes cannot get a proper list of members from structures that do have
members:


This accesses a "real" QRegionPrivate object in a 'QRegion region;':

  python print
gdb.parse_and_eval(\"region\")[\"d\"].dereference()[\"qt_rgn\"].dereference().type

  -> struct myns::QRegionPrivate
 
  python print
gdb.parse_and_eval(\"region\")[\"d\"].dereference()[\"qt_rgn\"].dereference().type.fields()

-> []


If I "create" the type manually I get:
 
  python print gdb.parse_and_eval(\"('myns::QRegionPrivate'*)0\").dereference().type
    -> myns::QRegionPrivate

  python print gdb.parse_and_eval(\"('myns::QRegionPrivate'*)0
\").dereference().type.fields()

    -> [<gdb.Field object at 0xb7764ac0>, <gdb.Field object at 0xb7764af0>,
<gdb.Field object at 0xb7764b20>, <gdb.Field object at 0xb7764b50>, <gdb.Field
object at 0xb7764b80>]

 
Note the extra "struct " in the 'type' output in the first case.

The problem also disappears when I use  type = gdb.lookup_type(str(type)) 
before accessing fields().

-- 
           Summary: Strange behaviour of gdb.Type.fields
           Product: gdb
           Version: 7.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: andre dot poenitz at nokia dot com
                CC: gdb-prs at sourceware dot org
 GCC build triplet: i486-linux-gnu
  GCC host triplet: i486-linux-gnu
GCC target triplet: i486-linux-gnu


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2010-07-01  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01  7:20 andre dot poenitz at nokia dot com [this message]
2010-07-01  7:35 ` [Bug python/11777] " andre dot poenitz at nokia dot com
2010-07-01  9:13 ` andre dot poenitz at nokia dot com
2010-07-06 19:52 ` tromey at redhat dot com
2010-08-20 18:27 ` 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=20100701072012.11777.andre.poenitz@nokia.com \
    --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).