This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Change how value is shown for varobjs of type vector.
- From: Tom Tromey <tromey at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Andrew Burgess <aburgess at broadcom dot com>, "gdb-patches\ at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 17 Oct 2012 11:04:29 -0600
- Subject: Re: [RFC] Change how value is shown for varobjs of type vector.
- References: <50631DE7.7050702@broadcom.com> <20121014172527.GC3050@adacore.com>
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Andrew> I have a patch (below) that changes the value field from the current
Andrew> "[8]" to "{ 0, 0, 0, 0, 0, 0, 0, 0 }". The varobj still has 8
Andrew> children, and the top level varobj is still not editable, you have to
Andrew> edit through the children.
Joel> I personally do not have a strong objection to this change, but I have
Joel> to admit that I am not particularly fond of the idea. I think that
Joel> this issue should be handled at the front-end level (Eg. Eclipse),
I think so too.
Marc> Although I haven't tried, I believe we can figure out this case
Marc> should be handled like the array case by improving Eclipse's type
Marc> parser to handle the vector_size __attribute__.
One thought I had was that, if gdb does not currently emit enough
information for Eclipse to treat vectors specially, then we could add a
"displayhint" field even to non-dynamic varobjs (or of course emit the
needed info in some other way).
Tom