From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andrew Burgess <aburgess@broadcom.com>,
"gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Change how value is shown for varobjs of type vector.
Date: Wed, 17 Oct 2012 17:04:00 -0000 [thread overview]
Message-ID: <87ehkx3u8y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20121014172527.GC3050@adacore.com> (Joel Brobecker's message of "Sun, 14 Oct 2012 10:25:27 -0700")
>>>>> "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
next prev parent reply other threads:[~2012-10-17 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 15:23 Andrew Burgess
2012-10-04 10:57 ` Andrew Burgess
2012-10-14 17:25 ` Joel Brobecker
2012-10-15 11:12 ` Marc Khouzam
2012-10-17 17:04 ` Tom Tromey [this message]
2012-10-18 9:23 ` Andrew Burgess
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=87ehkx3u8y.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=aburgess@broadcom.com \
--cc=brobecker@adacore.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