From: Tim Wiederhake <tim.wiederhake@intel.com>
To: gdb-patches@sourceware.org
Cc: palves@redhat.com, markus.t.metzger@intel.com
Subject: [PATCH v2 0/8] Python bindings for btrace recordings
Date: Fri, 04 Nov 2016 07:55:00 -0000 [thread overview]
Message-ID: <1478246074-14526-1-git-send-email-tim.wiederhake@intel.com> (raw)
This patch series adds Python bindings for btrace recordings.
V1 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2016-10/msg00733.html
Thanks to Eli and Simon for reviewing. Issues in V1 and changes in V2:
- Rebased on current master
- Patch 3:
- struct btrace_thread_info is memset to zero in some places. The VEC member
therefore can't be replaced by a std::vector at the moment.
- The linked list in struct btrace_function will go away in a follow up patch
series mentioned in Patch 3 "btrace: Use binary search to find instruction".
- Patch 4:
- New patch to remove logic from gdbpy_start_recording.
- Patch 5 (was 4):
- Commit message is now in present tense.
- Fixed typo: Function is gone.
- Variable in gdbpy_start_recording is now const.
- gdbpy_start_recording is now recording method agnostic.
- Python in target.{c,h}: I see no way around that. Ideas welcome.
See https://sourceware.org/ml/gdb-patches/2016-10/msg00803.html
- Patch 7 (was 6):
- Un-duplicated test name
- Renamed py-record.{c,exp} -> py-record-btrace.{c,exp}
- Patch 8 (was 7):
- Added references to process recording chapter.
- gdb.start_recording () now takes two arguments.
- Set brackets in roman typeface in documentation.
- Made it more clear that parameters to gdb.start_recording are strings.
Tim Wiederhake (8):
btrace: Count gaps as one instruction explicitly.
btrace: Export btrace_decode_error function.
btrace: Use binary search to find instruction.
Add record_start function.
python: Create Python bindings for record history.
python: Implement btrace Python bindings for record history.
python: Add tests for record Python bindings
Add documentation for new instruction record Python bindings.
gdb/Makefile.in | 12 +
gdb/NEWS | 4 +
gdb/btrace.c | 163 +++--
gdb/btrace.h | 21 +-
gdb/doc/python.texi | 237 ++++++
gdb/python/py-btrace.c | 996 ++++++++++++++++++++++++++
gdb/python/py-btrace.h | 32 +
gdb/python/py-record.c | 258 +++++++
gdb/python/py-record.h | 57 ++
gdb/python/python-internal.h | 7 +
gdb/python/python.c | 14 +
gdb/record-btrace.c | 131 ++--
gdb/record-full.c | 20 +
gdb/record.c | 28 +
gdb/record.h | 5 +
gdb/target-debug.h | 2 +
gdb/target-delegates.c | 33 +
gdb/target.c | 7 +
gdb/target.h | 10 +
gdb/testsuite/gdb.python/py-record-btrace.c | 48 ++
gdb/testsuite/gdb.python/py-record-btrace.exp | 160 +++++
21 files changed, 2107 insertions(+), 138 deletions(-)
create mode 100644 gdb/python/py-btrace.c
create mode 100644 gdb/python/py-btrace.h
create mode 100644 gdb/python/py-record.c
create mode 100644 gdb/python/py-record.h
create mode 100644 gdb/testsuite/gdb.python/py-record-btrace.c
create mode 100644 gdb/testsuite/gdb.python/py-record-btrace.exp
--
2.7.4
next reply other threads:[~2016-11-04 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 7:55 Tim Wiederhake [this message]
2016-11-04 7:55 ` [PATCH v2 6/8] python: Implement btrace Python bindings for record history Tim Wiederhake
2016-11-04 7:55 ` [PATCH v2 7/8] python: Add tests for record Python bindings Tim Wiederhake
2016-11-04 7:55 ` [PATCH v2 2/8] btrace: Export btrace_decode_error function Tim Wiederhake
2016-11-04 7:55 ` [PATCH v2 4/8] Add record_start function Tim Wiederhake
2016-11-04 7:55 ` [PATCH v2 3/8] btrace: Use binary search to find instruction Tim Wiederhake
2016-11-04 7:55 ` [PATCH v2 1/8] btrace: Count gaps as one instruction explicitly Tim Wiederhake
2016-11-04 7:55 ` [PATCH v2 8/8] Add documentation for new instruction record Python bindings Tim Wiederhake
2016-11-04 8:16 ` Eli Zaretskii
2016-11-04 7:55 ` [PATCH v2 5/8] python: Create Python bindings for record history Tim Wiederhake
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=1478246074-14526-1-git-send-email-tim.wiederhake@intel.com \
--to=tim.wiederhake@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.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