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: palves@redhat.com, markus.t.metzger@intel.com
Subject: [PATCH v2 0/1] btrace: Resume recording after disconnect.
Date: Tue, 19 Jul 2016 07:45:00 -0000	[thread overview]
Message-ID: <1468914307-31108-1-git-send-email-tim.wiederhake@intel.com> (raw)

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


             reply	other threads:[~2016-07-19  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  7:45 Tim Wiederhake [this message]
2016-07-19  7:45 ` [PATCH v2 1/1] " Tim Wiederhake
2016-07-21 16:17   ` Pedro Alves
2016-07-19 12:00 [PATCH v2 0/1] " Tim Wiederhake
2016-07-19 12:04 ` 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=1468914307-31108-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