This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: MI Interface and Pretty Print to_string() result
- From: Tom Tromey <tromey at redhat dot com>
- To: "Elmenthaler\, Jens" <jens dot elmenthaler at verigy dot com>
- Cc: <gdb at sourceware dot org>
- Date: Wed, 03 Mar 2010 15:14:05 -0700
- Subject: Re: MI Interface and Pretty Print to_string() result
- References: <daef60381002222308t530e0155w91640550858745af@mail.gmail.com> <58596C4646708B4BB990C4483997333001C49D91@usplmvpbe001.ent.rt.verigy.net>
- Reply-to: tromey at redhat dot com
>>>>> "Jens" == Elmenthaler, Jens <jens.elmenthaler@verigy.com> writes:
Sorry I didn't reply to this sooner.
Jens> If I see that right, there is no way to obtain the result of the
Jens> to_string() method from a pretty printer for a dynamic variable
Jens> object that is a child of another dynamic variable object.
Yeah.
Jens> -var-evaluate-expression returns "{...}" for anything that has
Jens> children, and in order to use -data-evaluate-expression, I must be
Jens> able to provide an expression that denotes the variable
Jens> object. This however, seems not possible for dynamic variable
Jens> objects that are a direct or indirect child of another dynamic
Jens> variable object.
Jens> Is there some mistake on my side?
Nope. I'm afraid this is just an unsolved problem with the
pretty-printers. Note that the to_string result is not going to
necessarily give you an expression, either.
I don't know about -data-evaluate-expression, but we also don't support
-var-info-path-expression:
http://sourceware.org/bugzilla/show_bug.cgi?id=10252
I haven't looked at this in a while, despite owning the PR, but my
recollection is that I didn't even have a good idea for how it could
work.
Tom