From: Doug Evans <dje@google.com>
To: Sasha Smundak <asmundak@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add Frame.read_register to Python API
Date: Wed, 03 Sep 2014 23:46:00 -0000 [thread overview]
Message-ID: <CADPb22T3H=8WLgzBSw6jEwFQkgTKxwVppsj+qKwsPkWaXqq0=g@mail.gmail.com> (raw)
In-Reply-To: <CADPb22SFmx06=Rg1O1g=3aAHBwtJnwA5rOzonv0_p--1WU35fw@mail.gmail.com>
On Fri, Aug 29, 2014 at 4:36 PM, Doug Evans <dje@google.com> wrote:
> On Fri, Aug 29, 2014 at 4:32 PM, Sasha Smundak <asmundak@google.com> wrote:
>> Thanks.
>> Here it is again:
>>
>>
>> The ability to read registers is needed to use Frame Filter API to
>> display the frames created by JIT compilers.
>>
>> gdb/ChangeLog:
>>
>> 2014-08-29 Sasha Smundak <asmundak@google.com>
>>
>>
>> * python/py-frame.c (frapy_read_register): New function.
>>
>> gdb/doc/ChangeLog
>>
>>
>> 2014-08-26 Sasha Smundak <asmundak@google.com>
>>
>> * python.texi (Frames in Python): Add read_register description.
>>
>> gdb/testsuite/ChangeLog:
>>
>>
>> 2014-08-26 Sasha Smundak <asmundak@google.com>
>>
>> * gdb.python/py-frame.exp: Test Frame.read_register.
>
> LGTM.
Hi.
fyi, I've committed this.
Thanks!
prev parent reply other threads:[~2014-09-03 23:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 19:15 Alexander Smundak
2014-06-09 19:26 ` Eli Zaretskii
2014-06-09 21:16 ` Alexander Smundak
2014-06-11 19:11 ` Tom Tromey
2014-06-11 23:52 ` Alexander Smundak
2014-06-18 17:18 ` Alexander Smundak
2014-06-18 17:33 ` Eli Zaretskii
2014-06-23 22:46 ` Alexander Smundak
2014-06-30 16:22 ` Alexander Smundak
2014-07-07 20:59 ` Alexander Smundak
2014-07-14 16:24 ` Alexander Smundak
2014-07-24 17:45 ` Doug Evans
2014-07-31 18:53 ` Doug Evans
2014-07-31 20:05 ` Tom Tromey
2014-08-21 18:44 ` Doug Evans
2014-08-26 20:31 ` Alexander Smundak
2014-08-29 13:39 ` Doug Evans
2014-08-29 23:32 ` Sasha Smundak
2014-08-29 23:36 ` Doug Evans
2014-09-03 23:46 ` Doug Evans [this message]
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='CADPb22T3H=8WLgzBSw6jEwFQkgTKxwVppsj+qKwsPkWaXqq0=g@mail.gmail.com' \
--to=dje@google.com \
--cc=asmundak@google.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).