From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: MI: -var-list-children --simple-values
Date: Thu, 16 Nov 2006 15:57:00 -0000 [thread overview]
Message-ID: <20061116155730.GB11539@nevyn.them.org> (raw)
In-Reply-To: <200611151929.29567.vladimir@codesourcery.com>
On Wed, Nov 15, 2006 at 07:29:28PM +0300, Vladimir Prus wrote:
> This is in fact completely different change. Here's
> what "-stack-list-locals --all-values" produces:
>
> ^done,locals=[{name="the_struct",value="{a_fr = 120, b = 333, inner_fr =
> {i = 0, j = 5, k = 5}, c = 3, pad = {0 <repeats 100 times>}, d =
> 10, pad2 = {0 <repeats 100 times>}, e = 10}"}]
>
> So, the difference between --all-values and --simple-values is dramatic. In
> case of --var-list-children you don't get full structure printed. You won't
> even have the structure *read* (with my laziness patch, that is).
>
> So, while --simple-values might be reasonable for -stack-list-locals, it's not
> all that needed for -var-list-children.
Hmm. I didn't realize that one use of --all-values printed out
structure contents and the other only "{...}" - I'm quite surprised.
I guess --simple-values and --all-values aren't so different then
for the varobj commands :-(
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-16 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611151250.11654.vladimir@codesourcery.com>
2006-11-15 11:21 ` Nick Roberts
2006-11-15 11:50 ` Vladimir Prus
2006-11-15 14:44 ` Daniel Jacobowitz
2006-11-15 14:55 ` Vladimir Prus
2006-11-15 15:09 ` Daniel Jacobowitz
2006-11-15 16:29 ` Vladimir Prus
2006-11-15 20:29 ` Nick Roberts
2006-11-29 9:35 ` Vladimir Prus
2006-11-29 9:58 ` Nick Roberts
2006-11-16 15:57 ` Daniel Jacobowitz [this message]
2006-11-15 19:55 ` Nick Roberts
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=20061116155730.GB11539@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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