Mirror of the gdb mailing list
 help / color / mirror / Atom feed
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: Sat, 19 Jan 2008 00:31:00 -0000	[thread overview]
Message-ID: <18321.17566.890207.913917@kahikatea.snap.net.nz> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA2DE09C@ecamlmw720.eamcs.ericsson.se>

 > > 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.
 > 
 > Can you elaborate?  When do you call var-update in this case?  Is it right
 > after the var-set-format?

Yes.  Emacs sends commands to GDB behind the user's back to update the display
every time the user initiates a GDB command himself.

You can see what Emacs 22.1 does quite easily.  You probably don't want to look
through thousands of lines of lisp code (gdb-ui.el) but you can just set
gdb-enable-debug to t and look at the value of gdb-debug-log after issuing some
commands to GDB in a session in Emacs (M-x gdb) so see the transactions.

In fact, I'd be interested to know how well (badly?) GDB in Emacs performs
in an embedded environment.

 > > I don't use -var-evaluate-expression for current GDB.
 > 
 > So how to you display a value in a different format (say hex)? You must be
 > calling -var-update right away after the set-format.  That is why I thought
 > "-var-set-format --all-values var1 hex" would return the value in hex (or
 > whatever format specified).  I'd use this too, as I wouldn't need to call
 > evaluate-expression after var-set-format.

"-var-update --all-values" returns the value in hex so currently I don't think
you need it in the output of "-var-set-format".  Previously, when the contents
were compared, I did submit a patch to add the value field to the output of
"-var-set-format" but it was never incorporated.  Note that, as stated in the
manual, new fields may be added to existing commands, so your existinng
frontend should be able to handle the parsing of these possible extra fields
and adding an option "--all-values" isn't necessary.  In fact, it's probably
undesirable because the frontend would have to test for the availability of
this option, rather than just the presence of the field in the output.

 > Then, you could say var-evaluate-expression is superfluous (I think).

I think I already have!

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-01-19  0:31 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 [this message]
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.17566.890207.913917@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