From: Tom Tromey <tromey@redhat.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC - GDB Python API] New gdb.Architecture class
Date: Wed, 23 Jan 2013 15:35:00 -0000 [thread overview]
Message-ID: <87a9rzx67p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAGyQ6gwTY59xn-g13Fk_E6s8+RuNO=D2WEh3N70jRMtP5NmE7w@mail.gmail.com> (Siva Chandra's message of "Wed, 23 Jan 2013 05:53:04 -0800")
>>>>> "Siva" == Siva Chandra <sivachandra@google.com> writes:
Siva> 2013-01-22 Siva Chandra Reddy <sivachandra@google.com>
Siva> Add a new class gdb.Architecture which exposes GDB's
Siva> internal representation of architecture via GDB Python API.
Siva> * Makefile.in: Add entries corresponding to the new file
Siva> python/py-arch.c.
Siva> * python/py-arch.c: Implement gdb.Architecture class.
Siva> * python/py-frame.c (frapy_arch): Implement the method
Siva> gdb.Frame.architecture().
Siva> (frame_object_methods): Add 'architecture' to the method table.
Siva> * python/python-internal.h: Add declarations of new utility
Siva> functions.
Siva> * python/python.c (_initialize_python): Initialize
Siva> gdb.Architecture class.
Siva> doc/
Siva> * gdb.texinfo (Architectures In Python): New sub-sub-section
Siva> describing the gdb.Architecture class.
Siva> (Frames In Python): Add description about the new method
Siva> Frame.architecture().
Siva> testsuite/
Siva> * gdb.python/frame.exp: Add a test for Frame.architecture()
Siva> method.
The code bits are ok.
It still needs a doc review though.
Tom
next prev parent reply other threads:[~2013-01-23 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 14:08 Siva Chandra
2013-01-21 17:09 ` Tom Tromey
2013-01-22 20:40 ` Siva Chandra
2013-01-22 21:17 ` Tom Tromey
2013-01-23 13:53 ` Siva Chandra
2013-01-23 15:35 ` Tom Tromey [this message]
2013-01-23 15:59 ` Eli Zaretskii
2013-01-23 21:01 ` Siva Chandra
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=87a9rzx67p.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.com \
/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