From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69470 invoked by alias); 19 Jul 2016 12:00:27 -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 69343 invoked by uid 89); 19 Jul 2016 12:00:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=news X-HELO: mga03.intel.com Received: from mga03.intel.com (HELO mga03.intel.com) (134.134.136.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 19 Jul 2016 12:00:12 +0000 Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 19 Jul 2016 05:00:07 -0700 X-ExtLoop1: 1 Received: from irvmail001.ir.intel.com ([163.33.26.43]) by FMSMGA003.fm.intel.com with ESMTP; 19 Jul 2016 05:00:06 -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 u6JC05rR025621; Tue, 19 Jul 2016 13:00:05 +0100 Received: from ulvlx001.iul.intel.com (localhost [127.0.0.1]) by ulvlx001.iul.intel.com with ESMTP id u6JC054k018552; Tue, 19 Jul 2016 14:00:05 +0200 Received: (from twiederh@localhost) by ulvlx001.iul.intel.com with œ id u6JC053v018548; Tue, 19 Jul 2016 14:00:05 +0200 From: Tim Wiederhake To: gdb-patches@sourceware.org Cc: palves@redhat.com, markus.t.metzger@intel.com Subject: [PATCH v2 0/1] btrace: Resume recording after disconnect. Date: Tue, 19 Jul 2016 12:00:00 -0000 Message-Id: <1468929605-18281-1-git-send-email-tim.wiederhake@intel.com> X-IsSubscribed: yes X-SW-Source: 2016-07/txt/msg00201.txt.bz2 Hi, thank you for your feedback. This is v2 of https://sourceware.org/ml/gdb-patches/2016-06/msg00165.html which fixes https://sourceware.org/ml/gdb-patches/2015-11/msg00420.html I followed Pedros suggestion about making "disconnect" not stop the trace, so the focus of this patch shifted a little bit to "new feature", away from "bugfix". - Tim Tim Wiederhake (1): btrace: Resume recording after disconnect. gdb/NEWS | 3 ++ gdb/doc/gdb.texinfo | 4 +- gdb/record-btrace.c | 51 ++++++++++++++++++------ gdb/record-btrace.h | 28 +++++++++++++ gdb/remote.c | 61 ++++++++++++++++++++++++++++ gdb/testsuite/gdb.btrace/reconnect.c | 25 ++++++++++++ gdb/testsuite/gdb.btrace/reconnect.exp | 73 ++++++++++++++++++++++++++++++++++ 7 files changed, 231 insertions(+), 14 deletions(-) create mode 100644 gdb/record-btrace.h create mode 100644 gdb/testsuite/gdb.btrace/reconnect.c create mode 100644 gdb/testsuite/gdb.btrace/reconnect.exp -- 2.7.4