This is the mail archive of the
mailing list for the Archer project.
Re: Access to "default GDB printer" from Python pretty printers?
- From: Tom Tromey <tromey at redhat dot com>
- To: ppluzhnikov at google dot com (Paul Pluzhnikov)
- Cc: archer at sourceware dot org
- Date: Wed, 05 Nov 2008 11:19:55 -0700
- Subject: Re: Access to "default GDB printer" from Python pretty printers?
- References: <20081105175721.C2DB73A6B0C@localhost>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Paul" == Paul Pluzhnikov <email@example.com> writes:
Paul> # Don't know how to print this kind of sockaddr.
Paul> # Just do whatever GDB would have done without Python.
Paul> return gdb.print_value(val)
The intent was to allow returning a value to bypass further
pretty-printing. The value_print / val_print thing messes with this a
But ... I'm working on getting rid of the function-style
pretty-printers altogether, per the note I sent a couple days ago.
I think simply returning the argument from to_string and children
won't work. We'd need a new way to do this.