Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Metzger <markus.t.metzger@intel.com>
To: jan.kratochvil@redhat.com, palves@redhat.com
Cc: gdb-patches@sourceware.org, markus.t.metzger@gmail.com
Subject: [PATCH] NEWS, btrace, gdbserver: mention btrace RSP packets in NEWS
Date: Mon, 08 Apr 2013 14:57:00 -0000	[thread overview]
Message-ID: <1365408794-12761-1-git-send-email-markus.t.metzger@intel.com> (raw)

This is for mainline and 7.6.

2013-04-08  Markus Metzger  <markus.t.metzger@intel.com>

	* NEWS: Mention new btrace RSP packets.


---
 gdb/NEWS |   18 ++++++++++++++++++
 1 files changed, 18 insertions(+), 0 deletions(-)

diff --git a/gdb/NEWS b/gdb/NEWS
index a1bc679..24f77b3 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -26,6 +26,24 @@ show remote trace-status-packet
 
 *** Changes in GDB 7.6
 
+* New RSP packets
+
+Qbtrace:bts
+
+  Enable Branch Trace Store (BTS)-based branch tracing for the current
+  thread.  The remote stub reports support for this packet to gdb's
+  qSupported query.
+
+Qbtrace:off
+
+  Disable branch tracing for the current thread.  The remote stub reports
+  support for this packet to gdb's qSupported query.
+
+qXfer:btrace:read
+
+  Read the traced branches for the current thread.  The remote stub
+  reports support for this packet to gdb's qSupported query.
+
 * Target record has been renamed to record-full.
   Record/replay is now enabled with the "record full" command.
   This also affects settings that are associated with full record/replay
-- 
1.7.1


             reply	other threads:[~2013-04-08  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 14:57 Markus Metzger [this message]
2013-04-08 16:04 ` Pedro Alves
2013-04-08 19:16 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2013-04-08 14:39 Markus Metzger
2013-04-08 14:57 ` Jan Kratochvil

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=1365408794-12761-1-git-send-email-markus.t.metzger@intel.com \
    --to=markus.t.metzger@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=markus.t.metzger@gmail.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