This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Patch: implement new dynamic varobj spec
- 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: Fri, 18 Sep 2009 12:25:25 -0600
- Subject: Re: Patch: implement new dynamic varobj spec
- References: <m3r5uejz4y.fsf@fleche.redhat.com> <h8vjtt$fqc$1@ger.gmane.org>
- Reply-to: tromey at redhat dot com
>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:
Volodya> 2. pretty-printer for string should catch exception and return
Volodya> "<inaccessible>" or some such. Alternatively, GDB should not
Volodya> fallback to regular display if Python pretty-printer fails. Yet
Volodya> alternatively, GDB should distinguish between different failure
Volodya> modes of Python pretty-printer, since memory access error
Volodya> likely to be caused by uninitalized data and should not cause
Volodya> fallback.
Volodya> Does this make any sense?
Yes. Of these options I lean more toward the last one.
However, I haven't thought carefully about it all yet.
Tom