This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: semantics of dynamic varobj
- From: Yao Qi <yao at codesourcery dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Sat, 23 Nov 2013 21:32:48 +0800
- Subject: Re: semantics of dynamic varobj
- Authentication-results: sourceware.org; auth=none
- References: <528F5839 dot 4050100 at codesourcery dot com> <87eh68e7qk dot fsf at fleche dot redhat dot com> <528F8856 dot 9030606 at redhat dot 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 (éå)