Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tim Wiederhake <tim.wiederhake@intel.com>
To: gdb-patches@sourceware.org
Cc: markus.t.metzger@intel.com, brobecker@adacore.com, qiyaoltc@gmail.com
Subject: [PATCH v2 0/8] Python bindings for GDB record
Date: Fri, 21 Apr 2017 10:50:00 -0000	[thread overview]
Message-ID: <1492771786-26372-1-git-send-email-tim.wiederhake@intel.com> (raw)

Hi all,

This patch series addresses the design issues with the Python bindings for
GDB record, as discussed here:
https://sourceware.org/ml/gdb-patches/2017-04/msg00171.html

V1 of this series can be found here:
https://sourceware.org/ml/gdb-patches/2017-04/msg00424.html

Changes since V1:
* error_string and error_code were renamed to reason_string and reason_code for
  gdb.RecordGap.
* Explicitly test retrieving recorded data from a non current thread.
* Moved some error handling code from patch #6 to patch #5.

Documentation was OK'd by Eli,
Patches #1, #4 and #8 were OK'd by Yao.

Please OK this series to go into master and the 8.0 branch.

Regards,
Tim

Tim Wiederhake (8):
  Python: Fix indentation in py-record-btrace.c
  Python: Fix exception handling in py-record-btrace.c
  Python: Use correct ptid in btrace recording
  Python: Remove ptid from gdb.Record interface
  Python: Introduce gdb.RecordGap class
  Python: Move and rename gdb.BtraceInstruction
  Python: Move and rename gdb.BtraceFunction
  Python: Introduce gdb.Instruction class

 gdb/Makefile.in                                    |   2 +
 gdb/btrace.c                                       |   8 +-
 gdb/doc/python.texi                                | 108 ++--
 gdb/python/py-instruction.c                        |  67 +++
 gdb/python/py-instruction.h                        |  30 +
 gdb/python/py-record-btrace.c                      | 618 ++++++++-------------
 gdb/python/py-record-btrace.h                      |  42 ++
 gdb/python/py-record.c                             | 424 +++++++++++++-
 gdb/python/py-record.h                             |  74 +++
 gdb/python/python-internal.h                       |   2 +
 gdb/python/python.c                                |   1 +
 .../gdb.python/py-record-btrace-threads.c          |  58 ++
 .../gdb.python/py-record-btrace-threads.exp        |  81 +++
 gdb/testsuite/gdb.python/py-record-btrace.exp      |   6 +-
 14 files changed, 1058 insertions(+), 463 deletions(-)
 create mode 100644 gdb/python/py-instruction.c
 create mode 100644 gdb/python/py-instruction.h
 create mode 100644 gdb/python/py-record.h
 create mode 100644 gdb/testsuite/gdb.python/py-record-btrace-threads.c
 create mode 100644 gdb/testsuite/gdb.python/py-record-btrace-threads.exp

-- 
2.7.4


             reply	other threads:[~2017-04-21 10:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 10:50 Tim Wiederhake [this message]
2017-04-21 10:50 ` [PATCH v2 8/8] Python: Introduce gdb.Instruction class Tim Wiederhake
2017-04-21 12:19   ` Eli Zaretskii
2017-04-24  5:34     ` Wiederhake, Tim
2017-04-21 18:10   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 4/8] Python: Remove ptid from gdb.Record interface Tim Wiederhake
2017-04-21 12:20   ` Eli Zaretskii
2017-04-21 10:50 ` [PATCH v2 7/8] Python: Move and rename gdb.BtraceFunction Tim Wiederhake
2017-04-21 12:22   ` Eli Zaretskii
2017-04-21 16:41   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 1/8] Python: Fix indentation in py-record-btrace.c Tim Wiederhake
2017-04-21 10:50 ` [PATCH v2 6/8] Python: Move and rename gdb.BtraceInstruction Tim Wiederhake
2017-04-21 12:23   ` Eli Zaretskii
2017-04-21 15:21   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 3/8] Python: Use correct ptid in btrace recording Tim Wiederhake
2017-04-21 14:49   ` Yao Qi
2017-04-21 10:50 ` [PATCH v2 2/8] Python: Fix exception handling in py-record-btrace.c Tim Wiederhake
2017-04-21 18:08   ` Yao Qi
2017-04-27 16:35   ` Pedro Alves
2017-04-21 10:50 ` [PATCH v2 5/8] Python: Introduce gdb.RecordGap class Tim Wiederhake
2017-04-21 12:25   ` Eli Zaretskii
2017-04-21 14:50   ` Yao Qi

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=1492771786-26372-1-git-send-email-tim.wiederhake@intel.com \
    --to=tim.wiederhake@intel.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=qiyaoltc@gmail.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