From: Eli Zaretskii <eliz@gnu.org>
To: Tim Wiederhake <tim.wiederhake@intel.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
markus.t.metzger@intel.com
Subject: Re: [PATCH v3 1/1] btrace: Resume recording after disconnect.
Date: Fri, 22 Jul 2016 09:55:00 -0000 [thread overview]
Message-ID: <83zipavvxy.fsf@gnu.org> (raw)
In-Reply-To: <1469179428-10333-2-git-send-email-tim.wiederhake@intel.com> (message from Tim Wiederhake on Fri, 22 Jul 2016 11:23:48 +0200)
> From: Tim Wiederhake <tim.wiederhake@intel.com>
> Cc: palves@redhat.com, markus.t.metzger@intel.com
> Date: Fri, 22 Jul 2016 11:23:48 +0200
>
> This patch allows gdbserver to continue recording after disconnect. On
> reconnect, the recorded data is accessible to gdb as if no disconnect happened.
Thanks.
> *** Changes since GDB 7.11
>
> +* GDBserver now supports record btrace without maintaining an active
> + GDB connection. ^^^^^^
I guess you meant "recording", because the above is not correct
English otherwise.
The documentation parts are okay with that fixed.
prev parent reply other threads:[~2016-07-22 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 9:24 [PATCH v3 0/1] " Tim Wiederhake
2016-07-22 9:24 ` [PATCH v3 1/1] " Tim Wiederhake
2016-07-22 9:55 ` Eli Zaretskii [this message]
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=83zipavvxy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.com \
--cc=tim.wiederhake@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).