From: Nick Roberts <nickrob@snap.net.nz>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: "Daniel Jacobowitz" <drow@false.org>, <gdb-patches@sources.redhat.com>
Subject: RE: [Patch] Fix for -var-update to use natural format to compare
Date: Wed, 23 Jan 2008 00:33:00 -0000 [thread overview]
Message-ID: <18326.35603.281821.709393@kahikatea.snap.net.nz> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04290E42@ecamlmw720.eamcs.ericsson.se>
> This is assuming the frontend only displays a single value.
> In DSF, we (sometimes) display all values at once. Can be nice for the user.
>
> > why do you want to keep track of the value in
> > all formats? And if you're actually displaying them all
> > simultaneously to the user, why shouldn't they be independent varobjs?
>
> Independent varObjects would work. However every time the program stops
> the frontend will need to issue a var-update on five objects instead of one,
> and what is worse is that GDB will need to read the memory from the target
> five times instead of once. This is less efficient than the frontend
> forcing GDB to use natural format (see below.)
You say it "Can be nice for the user." but you haven't really answered the
first question:
why do you want to keep track of the value in all formats?
Why, for example, would a user want to see the value of a double as a
decimal? It just seems to be a misleading thing to do.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-01-23 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 3:25 Marc Khouzam
2008-01-22 3:53 ` Daniel Jacobowitz
2008-01-22 14:43 ` Marc Khouzam
2008-01-22 15:03 ` Daniel Jacobowitz
2008-01-22 15:12 ` Marc Khouzam
2008-01-22 15:35 ` Vladimir Prus
2008-01-22 16:38 ` Marc Khouzam
2008-01-22 17:50 ` Vladimir Prus
2008-01-22 17:59 ` Daniel Jacobowitz
2008-01-23 0:33 ` Nick Roberts [this message]
2008-01-23 14:41 ` Marc Khouzam
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=18326.35603.281821.709393@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--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