From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: semantics of dynamic varobj
Date: Sat, 23 Nov 2013 13:34:00 -0000 [thread overview]
Message-ID: <5290AE80.8050103@codesourcery.com> (raw)
In-Reply-To: <528F8856.9030606@redhat.com>
On 11/23/2013 12:37 AM, Pedro Alves wrote:
> I no longer have the full context, but these varobjs are also
> only enabled when the client requests them (a new option
> to -var-create, IIRC). That is, a regular varobj will include both
> unavailable and available fields, with unavailable fields listed as
> "value=<unavailable>". For those, which fields are listed
> can be determined "statically", as usual, from the debug info. While
> this new varobj lists only the available fields, skipping the
> unavailable ones.
The option is "--available-children-only". I'll post the patches soon.
>
> (*) - Yao, as usual, the whole rationale for that should be
> in CS's internal archives.
Yes, I've got the mail in the archives.
--
Yao (é½å°§)
prev parent reply other threads:[~2013-11-23 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 13:14 Yao Qi
2013-11-22 13:28 ` Pedro Alves
2013-11-22 16:12 ` Tom Tromey
2013-11-22 16:37 ` Pedro Alves
2013-11-22 17:01 ` Tom Tromey
2013-11-23 13:34 ` Yao Qi [this message]
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=5290AE80.8050103@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.com \
/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