From: Doug Evans <xdje42@gmail.com>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, markus.t.metzger@intel.com,
palves@redhat.com
Subject: Re: [PATCH v6 7/9] python: Implement btrace Python bindings for record history.
Date: Mon, 13 Feb 2017 17:03:00 -0000 [thread overview]
Message-ID: <m3shniowfh.fsf@sspiff.org> (raw)
In-Reply-To: <1486989450-11313-8-git-send-email-tim.wiederhake@intel.com> (Tim Wiederhake's message of "Mon, 13 Feb 2017 13:37:28 +0100")
Tim Wiederhake <tim.wiederhake@intel.com> writes:
> This patch implements the gdb.Record Python object methods and fields for
> record target btrace. Also, implement a stub for record target full.
>
> 2017-02-13 Tim Wiederhake <tim.wiederhake@intel.com>
>
> gdb/ChangeLog:
>
> * Makefile.in (SUBDIR_PYTHON_OBS): Add py-record-btrace.o,
> py-record-full.o.
> (SUBDIR_PYTHON_SRCS): Add py-record-btrace.c, py-record-full.c.
> * python/py-record-btrace.c, python/py-record-btrace.h,
> python/py-record-full.c, python/py-record-full.h: New file.
> * python/py-record.c: Add include for py-record-btrace.h and
> py-record-full.h.
> (recpy_method, recpy_format, recpy_goto, recpy_replay_position,
> recpy_instruction_history, recpy_function_call_history, recpy_begin,
> recpy_end): Use functions from py-record-btrace.c and py-record-full.c.
> * python/python-internal.h (PyInt_FromSsize_t, PyInt_AsSsize_t):
> New definition.
> (gdbpy_initialize_btrace): New export.
> * python/python.c (_initialize_python): Add gdbpy_initialize_btrace.
LGTM
next prev parent reply other threads:[~2017-02-13 17:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 12:38 [PATCH v6 0/9] Python bindings for btrace recordings Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 4/9] Add record_start and record_stop functions Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 6/9] python: Create Python bindings for record history Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 3/9] btrace: Use binary search to find instruction Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 9/9] Add documentation for new record Python bindings Tim Wiederhake
2017-02-13 14:48 ` Eli Zaretskii
2017-03-03 11:10 ` Yao Qi
2017-03-06 8:56 ` Wiederhake, Tim
2017-03-07 11:53 ` Yao Qi
2017-03-07 17:23 ` Wiederhake, Tim
2017-03-17 16:50 ` Yao Qi
2017-02-13 12:38 ` [PATCH v6 5/9] Add method to query current recording method to target_ops Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 1/9] btrace: Count gaps as one instruction explicitly Tim Wiederhake
2017-02-13 12:38 ` [PATCH v6 2/9] btrace: Export btrace_decode_error function Tim Wiederhake
[not found] ` <1486989450-11313-8-git-send-email-tim.wiederhake@intel.com>
2017-02-13 17:03 ` Doug Evans [this message]
2017-02-13 17:12 ` [PATCH v6 7/9] python: Implement btrace Python bindings for record history Doug Evans
[not found] ` <1486989450-11313-9-git-send-email-tim.wiederhake@intel.com>
2017-02-13 17:17 ` [PATCH v6 8/9] python: Add tests for record Python bindings Doug Evans
2017-02-13 17:18 ` [PATCH v6 0/9] Python bindings for btrace recordings Doug Evans
2017-02-14 10:20 ` Wiederhake, Tim
2017-02-14 16:22 ` Doug Evans
2017-02-15 7:35 ` Wiederhake, Tim
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=m3shniowfh.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--cc=tim.wiederhake@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).