Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Document GDBserver fast tracepoints support in the manual
Date: Thu, 27 May 2010 18:18:00 -0000	[thread overview]
Message-ID: <83y6f5mdi7.fsf@gnu.org> (raw)
In-Reply-To: <201005271358.32190.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Thu, 27 May 2010 13:58:32 +0100
> 
> These are documentation bits originally posted along with this
> larger patch:
> 
>  [GDBserver fast tracepoints support]
>  <http://sourceware.org/ml/gdb-patches/2010-05/msg00149.html>
> 
> A few minor tweaks in the wording since the previous version,
> but largely the same.
> 
> Okay?

Yes, with a few minor comments:

> +@code{gdbserver} supports tracepoints on some target systems.  See
> +@ref{Tracepoints support in gdbserver}.

The last sentence should simply use @xref.

> +support the concept of preloading user defined libraries.  In most
> +cases, you do that by specifying @code{'LD_PRELOAD=libinproctrace.so'}
> +in the environment.

You don't need the '..' quotes inside @code.  If you want to make sure
the quotes will appear in print as well, use @samp.

> +Note that on most Unix systems, for the @code{dlopen} function be
> +available                                                     ^^^
   ^^^^^^^^^

"to be available", "to" is missing.

Thanks.


      reply	other threads:[~2010-05-27 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 14:50 Pedro Alves
2010-05-27 18:18 ` 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=83y6f5mdi7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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