Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com, lgustavo@codesourcery.com
Subject: Re: [PATCH v3 4/4] tracepoint multithread and multiprocess support (doc)
Date: Tue, 31 Dec 2013 08:10:00 -0000	[thread overview]
Message-ID: <834n5p1lxe.fsf@gnu.org> (raw)
In-Reply-To: <52C23A96.8090009@mentor.com>

> Date: Tue, 31 Dec 2013 11:31:34 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: Pedro Alves <palves@redhat.com>, <lgustavo@codesourcery.com>, Eli
>  Zaretskii <eliz@gnu.org>
> 
> This patch is for the doc.
> It add introduce of MultiThreadTracepoint and MultiProcessTracepointTogether.
> And add introduce of [:P@var{thread-id}] inside QTDP.

Thanks.

> 2013-12-31  Hui Zhu  <hui@codesourcery.com>
> 
> 	* gdb.texinfo (General Query Packets): Men[PATCH v3 4/4] tracepoint multithread and multiprocess support (doc)tion
> 	MultiThreadTracepoint and MultiProcessTracepointTogether feature.

Bad formatting of the ChangeLog entry.

> +@item MultiThreadTracepoint
> +@cindex string tracing, in remote protocol

This index entry sounds unrelated.  Copy/paste error?

> +The remote stub supports creation of tracepoints with multithread
> +infomation.
   ^^^^^^^^^^
Typo: should be "information"

> +@item MultiProcessTracepointTogether
> +@cindex string tracing, in remote protocol

This index entry also sounds unrelated.  Another copy/paste error?

> +The remote stub supports creation of tracepoints with multiprocess
> +infomation and the tracepoints of each inferior will be controlled
   ^^^^^^^^^^
Another typo.

OK with those gotchas fixed.


      reply	other threads:[~2013-12-31  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31  3:31 Hui Zhu
2013-12-31  8:10 ` 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=834n5p1lxe.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=lgustavo@codesourcery.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