From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72970 invoked by alias); 21 Apr 2017 10:50:08 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 72919 invoked by uid 89); 21 Apr 2017 10:50:07 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-10.6 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,GIT_PATCH_3,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*MI:tim, H*m:tim X-HELO: mga02.intel.com Received: from mga02.intel.com (HELO mga02.intel.com) (134.134.136.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 21 Apr 2017 10:50:06 +0000 Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Apr 2017 03:50:06 -0700 X-ExtLoop1: 1 Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga004.jf.intel.com with ESMTP; 21 Apr 2017 03:50:05 -0700 Received: from ulvlx001.iul.intel.com (ulvlx001.iul.intel.com [172.28.207.17]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id v3LAo4rC023762; Fri, 21 Apr 2017 11:50:04 +0100 Received: from ulvlx001.iul.intel.com (localhost [127.0.0.1]) by ulvlx001.iul.intel.com with ESMTP id v3LAo44U026629; Fri, 21 Apr 2017 12:50:04 +0200 Received: (from twiederh@localhost) by ulvlx001.iul.intel.com with œ id v3LAo3FC026625; Fri, 21 Apr 2017 12:50:03 +0200 From: Tim Wiederhake 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 Message-Id: <1492771786-26372-1-git-send-email-tim.wiederhake@intel.com> X-IsSubscribed: yes X-SW-Source: 2017-04/txt/msg00594.txt.bz2 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