Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make tracepoints into breakpoints
Date: Sat, 28 Mar 2009 09:07:00 -0000	[thread overview]
Message-ID: <uy6uqkoxu.fsf@gnu.org> (raw)
In-Reply-To: <49CD275B.1020003@codesourcery.com>

> Date: Fri, 27 Mar 2009 12:22:03 -0700
> From: Stan Shebs <stan@codesourcery.com>
> 
>     doc/
>     * gdb.texinfo (Tracepoints): Describe tracepoints as a
>     special case of breakpoints.
>     (Enable and Disable Tracepoints): Mention deprecation.
>     (Listing Tracepoints): Update description and example.

Thanks.  I have comments about this part:

>   Before running such a @dfn{trace experiment}, an arbitrary number of
> ! tracepoints can be set.  A tracepoint is actually a special type of
> ! breakpoint (@pxref{Set Breaks}), so you can manipulate it using
> ! standard breakpoint commands. For instance, as with breakpoints,
                                ^^
You have numerous places with only one space between sentences.

>   The @code{trace} command is very similar to the @code{break} command.
> ! Its argument @var{location} can be a source line, a function name, or
> ! an address in the target program.  @xref{Set Breaks}.  The
                                       ^^^^^^^^^^^^^^^^^
Please change this cross-reference to point to "Specify Location".

> ! In addition to the basic info common to all types of breakpoints,
> ! tracepoint listings may include a step count, a pass count, and the
> ! list of actions.

In this new text, you have removed the references to the tracepoint
parameters that affect the step count, the passcount, and the actions.
I think we should not drop those references, because they go a long
way towards explaining what these parameters are.

>                     The action lines are prefixed with an @code{A} so

Please use @samp{A} here, not @code{A}.  "A" is not a symbol, so it
should be quoted (in the printed output).

Other than that, the doco part of the patch is OK.


  reply	other threads:[~2009-03-28  8:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 19:57 Stan Shebs
2009-03-28  9:07 ` Eli Zaretskii [this message]
2009-03-30 16:10   ` Stan Shebs
2009-03-28 18:11 ` Eli Zaretskii
2009-03-30 15:44 ` Joel Brobecker
2009-03-30 16:56   ` Joel Brobecker
2009-03-30 18:29   ` Stan Shebs
2009-03-30 22:21     ` Joel Brobecker
2009-03-30 23:01       ` Stan Shebs
2009-03-30 22:07   ` Stan Shebs

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=uy6uqkoxu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@codesourcery.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