From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: -var-update using formatted value
Date: Sun, 20 Jan 2008 20:28:00 -0000 [thread overview]
Message-ID: <200801202327.30376.ghost@cs.msu.su> (raw)
In-Reply-To: <18323.43998.22471.788933@kahikatea.snap.net.nz>
On Sunday 20 January 2008 23:15:26 Nick Roberts wrote:
> > > > I cannot imagine any usecase where the frontend would:
> > > >
> > > > 1. Change format
> > > > 2. Step program
> > > > 3. Issue -var-update
> > >
> > > I'm not sure what point you're making here. Debugging GDB, has variables
> > > which contain addresses which are not pointers (so the natural format is
> > > decimal), e.g., stack_addr, code_addr components of frames. It makes
> > > sense here to:
> > >
> > > 1. Change format to hexadecimal
> > > 2. Step GDB
> > > 3. Issue -var-update to see if these values have changed.
> >
> > What UI-level command does this? And why, after you change format,
> > you don't read/display the value in new format?
>
> Creating a watch expression (in the speedbar, in the case of Emacs) for a frame
> related structure would do this. Yes, currently you would need to do
> -var-update after 1..
>
> Anyway, I withdraw my objection to your patch, if the patch (or similar) in the
> thread I mentioned (http://sourceware.org/ml/gdb-patches/2006-05/msg00008.html)
> is also approved. So there appears to be some consensus here.
FWIW, I agree that the patch in
http://sourceware.org/ml/gdb-patches/2006-05/msg00008.html
is good, as it removes the need to do -var-evaluate-expression
or -var-update after setting variable's format.
- Volodya
next prev parent reply other threads:[~2008-01-20 20:28 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
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 [this message]
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=200801202327.30376.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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