This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] python: Provide textual representation for Inferior and Objfile


>>>>> "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.

I could go either way about a NEWS entry.  It seems more like a
debugging convenience feature maybe?  Dunno.

The patch looks good.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]