From: Doug Evans <dje@google.com>
To: gdb-patches <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH, doc RFA] Add ability to set random attributes in python objfiles,progspaces
Date: Thu, 09 Oct 2014 19:10:00 -0000 [thread overview]
Message-ID: <CADPb22RD8FN-LQHykKV_XSWdijkcRdkco45awu8q4jq4sr3bkQ@mail.gmail.com> (raw)
In-Reply-To: <yjt27g09qcx2.fsf@ruffy.mtv.corp.google.com>
On Thu, Oct 9, 2014 at 12:08 PM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> I have a need to do some extra record keeping in progspaces and
> objfiles. This patch adds the ability to add random attributes
> to objfile and progspace objects using the same mechanism used
> for gdb.Fields.
>
> Regression tested on amd64-linux.
>
> 2014-10-09 Doug Evans <dje@google.com>
>
> * NEWS: Mention ability add attributes to gdb.Objfile and
> gdb.Progspace objects.
> * python/py-objfile.c (objfile_object): New member dict.
> (objfpy_dealloc): Py_XDECREF dict.
> (objfpy_initialize): Initialize dict.
> (objfile_getset): Add __dict__.
> (objfile_object_type): Set tp_dictoffset member.
> * python/py-progspace.c (progspace_object): New member dict.
> (pspy_dealloc): Py_XDECREF dict.
> (pspy_initialize): Initialize dict.
> (pspace_getset): Add __dict__.
> (pspace_object_type): Set tp_dictoffset member.
>
> doc/
> * gdb.texinfo (Progspaces In Python): Document ability to add
> random attributes to gdb.Progspace objects.
> (Objfiles In Python): Document ability to add random attributes to
> gdb.objfile objects.
>
> testsuite/
> * gdb.python/py-objfile.exp: Add tests for setting random attributes
> in objfiles.
> * gdb.python/py-progspace.exp: Add tests for setting random attributes
> in progspaces.
Oh, btw, if you're going to try this patch,
it depends on
https://sourceware.org/ml/gdb-patches/2014-10/msg00206.html
next parent reply other threads:[~2014-10-09 19:10 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 [this message]
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
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=CADPb22RD8FN-LQHykKV_XSWdijkcRdkco45awu8q4jq4sr3bkQ@mail.gmail.com \
--to=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