From: "Elmenthaler, Jens" <jens.elmenthaler@verigy.com>
To: <gdb@sourceware.org>
Subject: RE: MI Interface and Pretty Print to_string() result
Date: Thu, 04 Mar 2010 08:14:00 -0000 [thread overview]
Message-ID: <58596C4646708B4BB990C4483997333001D31204@usplmvpbe001.ent.rt.verigy.net> (raw)
In-Reply-To: <m34okx3vf6.fsf@fleche.redhat.com>
Tom> I don't know about -data-evaluate-expression, but we also don't support
Tom> -var-info-path-expression:
Tom> http://sourceware.org/bugzilla/show_bug.cgi?id=10252
Tom> I haven't looked at this in a while, despite owning the PR, but my
Tom> recollection is that I didn't even have a good idea for how it could
Tom> work.
If you could fix that, it would safe me (and possibly every other frontend) a lot of work! I'm close to deciding that enabling the pretty printers for the MI variable objects doesn't work.
The current issue is that if I have a pointer as a direct or indirect child of a dynamic variable object, how do I dereference it? The way it is done without pretty printers is to take the result of -var-info-path-expression, and than create a variable object for *(resulting-expression).
next prev parent reply other threads:[~2010-03-04 8:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 7:08 How to set default value of yquery and nquery Hui Zhu
2010-02-23 7:53 ` MI Interface and Pretty Print to_string() result Elmenthaler, Jens
2010-03-03 22:14 ` Tom Tromey
2010-03-04 8:14 ` Elmenthaler, Jens [this message]
2010-03-05 23:49 ` Tom Tromey
2010-03-07 10:16 ` Elmenthaler, Jens
2010-03-08 20:17 ` Tom Tromey
2010-02-23 17:13 ` How to set default value of yquery and nquery Tom Tromey
2010-02-24 6:08 ` Marc Khouzam
2010-02-24 9:53 ` Hui Zhu
2010-02-24 16:41 ` Marc Khouzam
2010-02-25 16:26 ` Hui Zhu
2010-02-26 0:23 ` Marc Khouzam
2010-02-26 17:31 ` Hui Zhu
2010-02-24 6:19 ` Hui Zhu
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=58596C4646708B4BB990C4483997333001D31204@usplmvpbe001.ent.rt.verigy.net \
--to=jens.elmenthaler@verigy.com \
--cc=gdb@sourceware.org \
/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