From: Phil Muldoon <pmuldoon@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: [PATCH, doc RFA] Add ability to set random attributes in python objfiles,progspaces
Date: Fri, 10 Oct 2014 18:25:00 -0000 [thread overview]
Message-ID: <5438247C.8050709@redhat.com> (raw)
In-Reply-To: <21560.6392.457864.907695@ruffy2.mtv.corp.google.com>
On 10/10/14 18:35, Doug Evans wrote:
> Phil Muldoon writes:
> > Maybe add a small example here as you did with gdb.Objfile? Or maybe
> > an xref. One of my goals in the next year is to add (and backfill in
> > existing documentation) more example led documentation for Python.
> > Sometimes an example speaks (ten) thousand words!
>
> I couldn't think of a simple one.
Maybe document (as in describe) a more complex one?
> > Thanks for this patch. It seems really useful (and in implementation
> > fairly simple to implement). I wonder if there are other objects in
> > Python that could benefit from the ability to arbitrarily record
> > keep?
>
> Like all things in gdb/python, things get added on a demand basis.
> [This observation extends to more pieces of gdb than just gdb/python.
> I'm happy to change the rules, but I do insist on there being
> no double standards. :-)]
Yes, I think this approach is the only way forward with Python, apart
from big feature patch-sets. I wasn't trying to sideline you into
providing this support for other objects btw! More a thinking "out
loud" where this functionality would be useful. So yeah, we'll add it
when we find we need it.
Cheers
Phil
next prev parent reply other threads:[~2014-10-10 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yjt27g09qcx2.fsf@ruffy.mtv.corp.google.com>
2014-10-09 19:10 ` Doug Evans
2014-10-10 7:58 ` Eli Zaretskii
2014-10-10 17:21 ` Doug Evans
2014-10-10 8:00 ` Phil Muldoon
2014-10-10 17:35 ` Doug Evans
2014-10-10 18:25 ` Phil Muldoon [this message]
2014-10-17 20:29 ` Doug Evans
2014-10-18 5:40 ` Eli Zaretskii
2014-10-21 16:53 ` Doug Evans
2014-10-21 18:23 ` Phil Muldoon
2014-10-31 0:07 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5438247C.8050709@redhat.com \
--to=pmuldoon@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox