How to get raw data with MI when pretty printing is enabled ?

How to get raw data with MI when pretty printing is enabled ?

[Sébastien Granjoux]

Hi,

The pretty printing display is easier to read. But if the data are wrong 
it can be useful to see exactly what is the content of a variable. Is it 
possible get this after using -enable-pretty-printing ?

As pretty-printing can change the number of children, I suppose it 
cannot be done using -var-set-format or something similar. But I think 
it would be useful if it is possible to create a new variable object 
which is not using pretty printer.

Regards,

Sébastien

Re: How to get raw data with MI when pretty printing is enabled ?

[asmwarrior]

On 2010-6-19 16:32, Sébastien Granjoux wrote:
> Hi,
>
> The pretty printing display is easier to read. But if the data are 
> wrong it can be useful to see exactly what is the content of a 
> variable. Is it possible get this after using -enable-pretty-printing ?
>
> As pretty-printing can change the number of children, I suppose it 
> cannot be done using -var-set-format or something similar. But I think 
> it would be useful if it is possible to create a new variable object 
> which is not using pretty printer.
>
> Regards,
>
> Sébastien
If you are not in MI mode, the command is like:

print /r YourVariableName



asmwarrior ollydbg from codeblocks' forum

Re: How to get raw data with MI when pretty printing is enabled ?

[Tom Tromey]

>>>>> "Sébastien" == Sébastien Granjoux <sebastien.granjoux@free.fr> writes:

Sébastien> As pretty-printing can change the number of children, I
Sébastien> suppose it cannot be done using -var-set-format or something
Sébastien> similar. But I think it would be useful if it is possible to
Sébastien> create a new variable object which is not using pretty
Sébastien> printer.

All the new features here are fully documented.  If you look through the
MI part of the manual and find that something is not there, or is
incorrect or unclear, please email or file a bug report so we can fix
it.

You can use -var-set-visualizer to disable pretty-printing of a given
varobj.

Tom

Re: How to get raw data with MI when pretty printing is enabled ?

[Sébastien Granjoux]

Hi Tom,

Le 21/06/2010 22:03, Tom Tromey a écrit :
> You can use -var-set-visualizer to disable pretty-printing of a given
> varobj.

I have tried but it doesn't work.

-var-create - * str_list
^done,name="var1",numchild="3",value="0x9ae2c90",type="GList 
*",thread-id="1",has_more="0"
(gdb)
-enable-pretty-printing
^done
(gdb)
-var-create - * str_list
^done,name="var2",numchild="0",value="{...}",type="GList 
*",thread-id="1",displayhint="array",dynamic="1",has_more="1"
(gdb)
-var-evaluate-expression var2
^done,value="{...}"
(gdb)
-var-evaluate-expression var1
^done,value="0x9ae2c90"
(gdb)
-var-set-visualizer var2 None
^done
(gdb)
-var-evaluate-expression var2
^done,value="{...}"
(gdb)

I would expect value="0x9ae2c90" for the last command. Then, I have use 
gdb version 7.0.50.20091001-cvs, perhaps it's working with the latest one.

Regards,

Sébastien

Re: How to get raw data with MI when pretty printing is enabled ?

[Tom Tromey]

>>>>> "Sébastien" == Sébastien Granjoux <seb.sfo@free.fr> writes:

Sébastien> -var-set-visualizer var2 None
Sébastien> ^done
Sébastien> (gdb)
Sébastien> -var-evaluate-expression var2
Sébastien> ^done,value="{...}"
Sébastien> (gdb)

Sébastien> I would expect value="0x9ae2c90" for the last command. Then, I have
Sébastien> use gdb version 7.0.50.20091001-cvs, perhaps it's working with the
Sébastien> latest one.

The test suite does a -var-update instead of -var-evaluate-expression.
Could you try that instead?

I'm not completely sure if the above is intended to work or not.
Please file a bug report, in case it is supposed to.

thanks,
Tom

Re: How to get raw data with MI when pretty printing is enabled ?

[Sébastien Granjoux]

Hi,

Le 21/06/2010 23:24, Tom Tromey a écrit :
> The test suite does a -var-update instead of -var-evaluate-expression.
> Could you try that instead?

Yes, it's working then. -var-list-children is working as expected too. 
Setting the visualizer to None, remove the pretty printer, while setting 
to gdb.default_visualizer restore it.

> I'm not completely sure if the above is intended to work or not.
> Please file a bug report, in case it is supposed to.

I don't know neither. I have filled a bug report
http://sourceware.org/bugzilla/show_bug.cgi?id=11738

Regards,

Sébastien

-var-set-visualizer to dynamically switch pretty print on and off?

[Elmenthaler, Jens]

> You can use -var-set-visualizer to disable pretty-printing of a given
> varobj.
> 
> Tom
Does that mean I can use -var-set-visualizer to dynamically switch between pretty printers on and off during a debug session, and this even individually for each varobj? That would be a nice feature!

Jens.

Re: -var-set-visualizer to dynamically switch pretty print on and off?

[Tom Tromey]

>>>>> "Jens" == Elmenthaler, Jens <jens.elmenthaler@verigy.com> writes:

Tom> You can use -var-set-visualizer to disable pretty-printing of a given
Tom> varobj.

Jens> Does that mean I can use -var-set-visualizer to dynamically switch
Jens> between pretty printers on and off during a debug session, and
Jens> this even individually for each varobj? That would be a nice
Jens> feature!

Yes.  Dynamic varobjs have other nice features, too -- you can lazily
fetch the children.  It is all in the manual... let us know if it is
unclear in some way.

Tom