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: Wed, 15 Nov 2006 15:09:00 -0000 [thread overview]
Message-ID: <20061115150940.GA26174@nevyn.them.org> (raw)
In-Reply-To: <200611151755.02301.vladimir@codesourcery.com>
On Wed, Nov 15, 2006 at 05:55:02PM +0300, Vladimir Prus wrote:
> Why? Especially, why it's better than --all-values. Note that --simple-values
> only don't print values of arrays, structures and unions, and if you check
> c_value_of_variable, you'll see that for structures just a literal string is
> returned, while for array very trivial formatting operation is used.
>
> In other words, --all-values do not involve any complex processing, reading
> data from the target, or anything. What are we trying to save by
> adding --simple-values?
But the result of --all-values where it differs from --simple-values is
probably not used. I've never used an IDE that printed out the
collapsed value of a struct; instead it wants an expandable item
for each struct member. --simple-values is for things without
children.
I didn't invent --simple-values though, I just added it to -var-update.
Nick added it to -stack-list-locals on 20-Jan-2004. Ah here:
http://sourceware.org/ml/gdb/2003-11/msg00055.html
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-15 15:09 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 [this message]
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
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=20061115150940.GA26174@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