public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA] mi/10586
Date: Tue, 13 Dec 2011 01:28:00 -0000	[thread overview]
Message-ID: <4EE67462.5040203@redhat.com> (raw)
In-Reply-To: <4ED95103.8030204@redhat.com>

Ping

On 12/02/2011 02:28 PM, Keith Seitz wrote:
> On 11/15/2011 09:10 AM, Keith Seitz wrote:
>> On 11/14/2011 12:28 PM, Tom Tromey wrote:
>>
>>> Actually, thinking about it more, it seems to me that it would be ok for
>>> these cases to just be errors. There's no really good way to refer to
>>> the anonymous field as its own entity, and I don't think we should hack
>>> up the parser and whatever else to support this.
>>
>> An error... I'm not so sure that I like that, but to be honest, I'm not
>> sure I like/dislike it sufficiently to argue about it.
>
> Ok, so in the end, I've decided against making this an error. Instead,
> what I've implemented is analogous to how varobj/MI currently deal with
> the CPLUS_FAKE_CHILD cases: path expressions and the like are "".
>
> If you would like me to do otherwise, please let me know.
>
> I am attaching the latest incarnation of this patch, which covers all
> these cases (AFAIK) and utilizes the new varobj tree testing that I
> committed last week.
>
> What do you think?
>
> Keith
>
> ChangeLog
> 2011-12-02 Keith Seitz <keiths@redhat.com>
>
> PR mi/10586
> Based on work by Nick Roberts <nickrob@snap.net.nz>:
> * varobj.c [ANONYMOUS_STRUCT_NAME]: New constant.
> [ANONYMOUS_UNION_NAME]: Likewise.
> (is_anonymous_child): New function.
> (create_child_with_value): If the child is nameless,
> synthesize a name for it.
> (c_describe_child): If the child has no field or type names
> for a union or sturct, use ANONYMOUS_STRUCT_NAME or
> ANONYMOUS_UNION_NAME.
> Set path expression for these fields to the empty string.
> (cplus_describe_child): Likewise.
> (is_path_expr_parent): New function.
> (get_path_expr_parent): New function.
>
> testsuite/ChangeLog
> 2011-12-02 Keith Seitz <keiths@redhat.com>
>
> PR mi/10586
> * gdb.mi/mi-var-cp.cc (anonymous_structs): New function.
> (class A): New class.
> (class B): New class.
> (main): Call anonymous_structs.
> * gdb.mi/mi-var-cp.exp: Add anonymous struct tests and
> adjust test results.
> * gdb.mi/mi2-var-cp.exp: Likewise.
> * gdb.mi/var-cmd.c (struct _simple_struct): Add two anonymous
> structs.
> * gdb.mi/mi-var-dislay.exp: Add anonymous struct tests and
> adjust test results.
> * gdb.mi/mi2-var-display.exp: Likewise.

  reply	other threads:[~2011-12-12 21:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 21:30 Keith Seitz
2011-11-14 15:45 ` Tom Tromey
2011-11-14 18:04   ` Keith Seitz
2011-11-14 18:18     ` Tom Tromey
2011-11-14 19:28       ` Keith Seitz
2011-11-14 20:28         ` Tom Tromey
2011-11-15 17:10           ` Keith Seitz
2011-11-15 17:30             ` Tom Tromey
2011-12-02 22:28             ` Keith Seitz
2011-12-13  1:28               ` Keith Seitz [this message]
2011-12-13 19:58               ` Tom Tromey
2011-12-17  1:55                 ` Keith Seitz
2011-12-20 16:03                   ` Tom Tromey
2012-01-12 23:05                     ` Keith Seitz
2011-12-13 20:34               ` Crash regression with Eclipse [Re: [RFA] mi/10586] Jan Kratochvil

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=4EE67462.5040203@redhat.com \
    --to=keiths@redhat.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).