Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>
Cc: "Daniel Jacobowitz" <drow@false.org>, 	<gdb-patches@sourceware.org>
Subject: RE: [Patch] -var-evaluate-expression NAME [FORMAT]
Date: Mon, 04 Feb 2008 21:40:00 -0000	[thread overview]
Message-ID: <18343.34335.642831.945359@kahikatea.snap.net.nz> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04290E86@ecamlmw720.eamcs.ericsson.se>

 > My patch no longer works with the patch Vladimir applied
 > http://sourceware.org/ml/gdb/2008-02/msg00006.html
 > The reason is that Vladimir's patch has c_value_of_variable()
 > always use the stored print_value which is formatted based on the
 > current display format (and not the one specified as an option
 > to -var-evaluate-expression.)  I think that is a good way to do it.
 > 
 > One solution is to revert c_value_of_variable:
 > -           return xstrdup (var->print_value);
 > +           return value_get_print_value (var->value, var->format);
 > 
 > Although this is very easy, personally, I don't like that too much.
 > 
 > Another option is to not only temporarily set var->format
 > but also var->print_value (by calling varobj_set_display_format).
 > I like this even less.
 > 
 > I think a solution based on 
 > http://sourceware.org/ml/gdb-patches/2008-01/msg00531.html
 > is probably the cleanest.  Can I have an educated opinion on
 > this decision?

This also uses value_get_print_value in c_value_of_variable.  I can't seem
to apply your earlier patch as I get spurious characters when I save it
(= -> =3D, \n -> =20\n, etc) but I wonder if we've made things too complicated.

What happens if you just use value_get_print_value (var->value, var->format)
directly in mi_cmd_var_evaluate_expression instead of varobj_get_value (var)?

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


  reply	other threads:[~2008-02-04 21:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 20:38 Marc Khouzam
2008-01-23  3:04 ` Nick Roberts
2008-01-23 14:30   ` Marc Khouzam
2008-01-23 14:42     ` Daniel Jacobowitz
2008-01-23 17:04       ` Marc Khouzam
2008-01-23 22:09         ` Nick Roberts
2008-01-24 21:36           ` Marc Khouzam
2008-01-25  9:59             ` Eli Zaretskii
2008-01-29 21:45             ` Daniel Jacobowitz
2008-02-01 19:23               ` Marc Khouzam
2008-02-02 10:31                 ` Eli Zaretskii
2008-02-03 19:43                   ` Marc Khouzam
2008-02-03 20:01                     ` Eli Zaretskii
2008-02-04 14:17                       ` Marc Khouzam
2008-02-04 21:00                         ` Eli Zaretskii
2008-02-02 11:20                 ` Vladimir Prus
2008-02-03 19:55                   ` Marc Khouzam
2008-02-03 20:42                     ` Joel Brobecker
2008-02-03 21:41                       ` Daniel Jacobowitz
2008-02-03 21:46                 ` Daniel Jacobowitz
2008-02-04 17:00                   ` Marc Khouzam
2008-02-04 17:02                   ` Marc Khouzam
2008-02-04 21:40                     ` Nick Roberts [this message]
2008-02-04 21:53                       ` Nick Roberts
2008-02-05 14:47                       ` Marc Khouzam
2008-02-05 20:43                         ` Nick Roberts
2008-02-05 20:55                           ` Marc Khouzam
2008-02-05 21:18                             ` Nick Roberts
2008-02-04 17:11                   ` Marc Khouzam
2008-01-23  3:48 ` Daniel Jacobowitz
2008-01-23 14:44   ` Marc Khouzam
2008-01-28 14:41 Marc Khouzam
2008-01-28 14:48 ` Daniel Jacobowitz

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=18343.34335.642831.945359@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@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