Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <hui_zhu@mentor.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: [PATCH v2 4/4] tracepoint multithread and multiprocess support (doc)
Date: Thu, 19 Dec 2013 03:33:00 -0000	[thread overview]
Message-ID: <52B268F2.2060206@mentor.com> (raw)

This version doesn't have big change, just update follow GDB trunk
and update Changelog.

This patch is for the doc.
Please help me review it.

Thanks,
Hui

2013-12-19  Hui Zhu  <teawater@gmail.com>

	* gdb.texinfo (General Query Packets): Mention
	MultiProcessTracepoint feature.
	(QTDP): Add 'P'.

--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -39616,6 +39616,11 @@ These are the currently defined stub fea
  @tab @samp{-}
  @tab No
  
+@item @samp{MultiProcessTracepoint}
+@tab No
+@tab @samp{-}
+@tab No
+
  @end multitable
  
  These are the currently defined stub features, in more detail:
@@ -39789,6 +39794,12 @@ The remote stub understands the @samp{Qb
  @item Qbtrace:bts
  The remote stub understands the @samp{Qbtrace:bts} packet.
  
+@item MultiProcessTracepoint
+@cindex string tracing, in remote protocol
+The remote stub supports creation of tracepoints with multiprocess
+and multithread infomation.
+@xref{Tracepoint Packets}.
+
  @end table
  
  @item qSymbol::
@@ -40316,7 +40327,7 @@ tracepoints (@pxref{Tracepoints}).
  
  @table @samp
  
-@item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:X@var{len},@var{bytes}]@r{[}-@r{]}
+@item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:P@var{thread-id}][:X@var{len},@var{bytes}]@r{[}-@r{]}
  @cindex @samp{QTDP} packet
  Create a new tracepoint, number @var{n}, at @var{addr}.  If @var{ena}
  is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then
@@ -40324,7 +40335,10 @@ the tracepoint is disabled.  @var{step}
  count, and @var{pass} is its pass count.  If an @samp{F} is present,
  then the tracepoint is to be a fast tracepoint, and the @var{flen} is
  the number of bytes that the target should copy elsewhere to make room
-for the tracepoint.  If an @samp{X} is present, it introduces a
+for the tracepoint.  If a @samp{P} is present, the thread designator
+@var{thread-id} that has the format and interpretation described in
+@ref{thread-id syntax} includes the multiprocess and multithread infomation
+of this tracepoint.  If an @samp{X} is present, it introduces a
  tracepoint condition, which consists of a hexadecimal length, followed
  by a comma and hex-encoded bytes, in a manner similar to action
  encodings as described below.  If the trailing @samp{-} is present,


             reply	other threads:[~2013-12-19  3:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  3:33 Hui Zhu [this message]
2013-12-19  3:52 ` Eli Zaretskii

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=52B268F2.2060206@mentor.com \
    --to=hui_zhu@mentor.com \
    --cc=gdb-patches@sourceware.org \
    /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