This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] python: Provide textual representation for Inferior and Objfile
- From: Simon Marchi <simon dot marchi at polymtl dot ca>
- To: Tom Tromey <tom at tromey dot com>
- Cc: Simon Marchi <simon dot marchi at ericsson dot com>, gdb-patches at sourceware dot org
- Date: Wed, 12 Sep 2018 18:10:45 -0400
- Subject: Re: [PATCH] python: Provide textual representation for Inferior and Objfile
- References: <20180912205449.12836-1-simon.marchi@ericsson.com> <87zhwmid4p.fsf@tromey.com>
On 2018-09-12 18:07, Tom Tromey wrote:
"Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:
Simon> This makes printing debug traces more difficult than it should
be. This
Simon> patch provides some repr() implementation for these two types
(more to
Simon> come if people agree with the idea, but I want to test the water
first).
I think it is a good idea.
Simon> In your opinion, does this require an announcement in NEWS and
an entry
Simon> in the manual? I don't think the output of repr() should be
considered
Simon> stable, as we could change it over time to make it more useful.
Maybe
Simon> that should be documented?
That seems like a reasonable rule to me. One idea would be to make
this
a general rule for the gdb Python layer and document it in the "Basic
Python" node.
Good idea, a blanket warning (for string repr of all object types) in
there should be enough. I'll do it that.
I could go either way about a NEWS entry. It seems more like a
debugging convenience feature maybe? Dunno.
That's what I think too.
Thanks,
Simon