From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [patch] ptype: show members of an unnamed struct inside an union
Date: Wed, 29 Aug 2007 20:44:00 -0000 [thread overview]
Message-ID: <20070829204423.GA16129@caradoc.them.org> (raw)
In-Reply-To: <20070829204114.GH3795@adacore.com>
On Wed, Aug 29, 2007 at 01:41:14PM -0700, Joel Brobecker wrote:
> The one reason I think it's a good idea to expand the field description
> when the field does not have a name, is because there is no way to
> get that information otherwise. But in the case of a named field that
> has an anonymous type, we can easily get the type information simply
> by selecting it (I mean by that: "ptype my_page.u" where u is the field
> name of your union).
That's not quite true. You need a variable, or to mess around with
casting a pointer; you can't say "ptype my_type.member".
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-08-29 20:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 22:39 Carlos Eduardo Seo
2007-08-24 15:48 ` Joel Brobecker
2007-08-24 16:02 ` Carlos Eduardo Seo
2007-08-24 17:39 ` Joel Brobecker
2007-08-28 17:14 ` Joel Brobecker
2007-08-28 19:03 ` Luis Machado
2007-08-28 20:04 ` Joel Brobecker
2007-08-28 20:12 ` Carlos Eduardo Seo
2007-08-28 20:34 ` Joel Brobecker
2007-08-29 2:56 ` Daniel Jacobowitz
2007-08-29 4:36 ` Joel Brobecker
2007-08-29 16:30 ` Daniel Jacobowitz
2007-08-29 18:32 ` Joel Brobecker
2007-08-29 18:36 ` Daniel Jacobowitz
2007-08-29 18:48 ` Joel Brobecker
2007-08-29 18:50 ` Carlos Eduardo Seo
2007-08-29 20:14 ` Carlos Eduardo Seo
2007-08-29 20:23 ` Daniel Jacobowitz
2007-08-29 20:26 ` Carlos Eduardo Seo
2007-08-29 20:41 ` Joel Brobecker
2007-08-29 20:44 ` Daniel Jacobowitz [this message]
2007-08-29 21:01 ` Joel Brobecker
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=20070829204423.GA16129@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@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