This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Python pretty-printing [6/6]
- From: Tom Tromey <tromey at redhat dot com>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 18 May 2009 17:34:11 -0600
- Subject: Re: Python pretty-printing [6/6]
- References: <m37i22bwoq.fsf@fleche.redhat.com> <loom.20090518T052234-940@post.gmane.org>
- Reply-to: tromey at redhat dot com
>>>>> "Vladimir" == Vladimir Prus <vladimir@codesourcery.com> writes:
Vladimir> 1. From the *MI* docs it is not apparent why the
Vladimir> 'visualizer' passed is called with varobj to get the real
Vladimir> visualizer. Docs probably should be more explicit.
I will update the docs.
Vladimir> 2. I am unsure about the -var-set-child-range function --
Vladimir> why is this an integral part of this patch? Was this tried
Vladimir> with any frontend, and found sufficient/good? I don't think
Vladimir> we ever reached a conclusion as to how to deal with big
Vladimir> number of children.
Yes, it is not intrinsically related. However, it is very easy for
users to end up with huge objects when a pretty-printer is installed.
That is, I think pretty-printing makes an existing problem more
noticeable.
AFAIK, no front end is currently using this function. So, I can
remove it if you would prefer that.
Tom