From: Nick Roberts <nickrob@snap.net.nz>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: <gdb@sourceware.org>
Subject: RE: -var-update using formatted value
Date: Fri, 18 Jan 2008 21:10:00 -0000 [thread overview]
Message-ID: <18321.5512.90696.545727@kahikatea.snap.net.nz> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA2DE096@ecamlmw720.eamcs.ericsson.se>
> > I don't like this change. If I change the format to hexadecimal, 11 -> 0xb
> > say, the display should change, so I would like GDB to report it through
> > -var-update.
>
> > Previously -var-evaluate-expression was needed because values weren't
> > displayed when variable objects were created (-var-create now includes the
> > value field, -var-list-children has the --all-values option). Given that
> > -var-update provides a record of all changes, I'm not sure that
> > -var-evaluate-expression is necessary now.
>
> It is starting to come together now :-)
> What you are missing is for -var-set-format to have the --all-values flag.
> Then, I believe you can stop using -var-evaluate-expression. Using
> -var-update instead of var-evaluate-expression or -var-set-format
> --all-values seems kind of a hack...
I don't use -var-evaluate-expression for current GDB.
> What do you think of that? Vladimir's patch and --all-values in set-format?
> To me, it seems like the proper solution.
If I don't like Vladimir's patch on its own, I don't see why I should like it
with --all-values in -var-set-format. But I'm probably missing your point.
What would "-var-set-format --all-values" return? The value in the current
format or all formats?
When GDB stops I use "-var-update --all-values" to find out which watch
expressions have changed. What are you proposing that I should use?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-01-18 21:10 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 15:13 Marc Khouzam
2008-01-11 17:40 ` Vladimir Prus
2008-01-11 18:31 ` Marc Khouzam
2008-01-11 19:40 ` Marc Khouzam
2008-01-11 22:26 ` Nick Roberts
2008-01-11 22:53 ` Andreas Schwab
2008-01-11 22:59 ` Daniel Jacobowitz
2008-01-11 23:40 ` Nick Roberts
2008-01-11 23:52 ` Daniel Jacobowitz
2008-01-12 3:41 ` Marc Khouzam
2008-01-12 3:49 ` Daniel Jacobowitz
2008-01-14 2:36 ` Marc Khouzam
2008-01-15 18:43 ` Vladimir Prus
2008-01-15 19:36 ` Marc Khouzam
2008-01-15 20:32 ` Vladimir Prus
2008-01-17 14:57 ` Marc Khouzam
2008-01-17 18:05 ` Vladimir Prus
2008-01-18 1:35 ` Nick Roberts
2008-01-18 15:31 ` Marc Khouzam
2008-01-18 15:41 ` Daniel Jacobowitz
2008-01-18 17:17 ` Marc Khouzam
2008-01-18 17:53 ` Daniel Jacobowitz
2008-01-18 19:26 ` Marc Khouzam
2008-01-18 21:10 ` Nick Roberts [this message]
2008-01-18 22:21 ` Marc Khouzam
2008-01-19 0:31 ` Nick Roberts
2008-01-19 1:46 ` Marc Khouzam
2008-01-19 8:27 ` Nick Roberts
2008-01-19 11:17 ` Vladimir Prus
2008-01-21 15:47 ` Marc Khouzam
2008-01-21 21:44 ` Nick Roberts
2008-01-17 23:10 ` Nick Roberts
2008-01-19 11:06 ` Vladimir Prus
2008-01-19 22:02 ` Nick Roberts
2008-01-20 10:04 ` Vladimir Prus
2008-01-20 20:16 ` Nick Roberts
2008-01-20 20:28 ` Vladimir Prus
2008-01-21 15:15 ` Marc Khouzam
2008-01-21 22:35 ` Nick Roberts
2008-01-29 21:20 ` Daniel Jacobowitz
2008-02-03 22:21 ` Nick Roberts
2008-02-04 6:15 ` Vladimir Prus
2008-01-18 0:53 ` Nick Roberts
2008-01-18 2:13 ` Marc Khouzam
2008-01-18 21:00 ` Nick Roberts
2008-01-18 22:04 ` Marc Khouzam
2008-01-14 6:34 ` Nick Roberts
2008-01-29 21:26 ` Daniel Jacobowitz
2008-01-29 23:49 ` Nick Roberts
2008-01-30 0:04 ` Daniel Jacobowitz
2008-01-30 4:25 ` 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=18321.5512.90696.545727@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.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