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 c++/13615] New: inherited typedefs not found properly
Date: Mon, 23 Jan 2012 18:21:00 -0000	[thread overview]
Message-ID: <bug-13615-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13615
           Summary: inherited typedefs not found properly
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned@sourceware.org
        ReportedBy: tromey@redhat.com
    Classification: Unclassified


Consider this program:

struct Base {
  typedef int value_type;
};

struct Derived : public Base {
  value_type x;
};

Derived d;
Derived::value_type v;


Compile this with '-g -c' and run gdb on the .o.
Now some type lookups work, but some do not:

(gdb) ptype Derived::value_type
type = int
(gdb) p (Derived::value_type *) 0
A syntax error in expression, near `) 0'.
(gdb) p (Base::value_type *) 0
A syntax error in expression, near `) 0'.
(gdb) python print gdb.lookup_type('Derived::value_type')
Traceback (most recent call last):
  File "<string>", line 1, in <module>
RuntimeError: No type named Derived::value_type.
Error while executing Python code.
(gdb) python print gdb.lookup_type('Base::value_type')
Base::value_type

-- 
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-01-23 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 18:21 tromey at redhat dot com [this message]
2012-01-23 21:20 ` [Bug c++/13615] " jan.kratochvil at redhat dot com
2012-11-16 20:54 ` cvs-commit at gcc dot gnu.org
2012-11-16 20:56 ` keiths 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-13615-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).