From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Document task-specific breakpoints
Date: Thu, 09 Apr 2009 17:19:00 -0000 [thread overview]
Message-ID: <8363hd4uhq.fsf@gnu.org> (raw)
In-Reply-To: <20090409165926.GJ7535@adacore.com>
> Date: Thu, 9 Apr 2009 09:59:26 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>
> > Joel> +It is also possible to insert a breakpoint that will stop the program
> > Joel> +only if a specific thread or a specific task hits that breakpoint.
> > Joel> +@xref{Thread-Specific Breakpoints} and @ref{Ada Tasks} for more
> >
> > ../../../archer/gdb/doc/gdb.texinfo:3057: warning: `.' or `,' must follow @xref, not `a'.
>
> Umpf :-(, sorry about that. Is it OK if I add a coma after the xref.
Yes, that's the canonical way of handling this. Note that @ref also
needs a comma after its argument.
> See Thread-Specific Breakpoints, and Ada Tasks for more [...]
>
> I would have prefered the current version, though.
Right, but this is a limitation of Texinfo.
> Perhaps we need to change the way we wrote the references?
In general, it is not a very good idea to have several
cross-references to close in the same sentence. Something like the
following might be better:
@xref{Thread-Specific Breakpoints}, for more about this. For
Ada-specific aspects, see @ref{Ada Tasks}.
next prev parent reply other threads:[~2009-04-09 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 22:02 Joel Brobecker
2009-03-25 22:11 ` Joel Brobecker
2009-03-26 13:10 ` Eli Zaretskii
2009-03-26 22:50 ` Joel Brobecker
2009-03-27 11:56 ` Eli Zaretskii
2009-03-27 15:39 ` Joel Brobecker
2009-03-27 15:50 ` Eli Zaretskii
2009-03-27 16:11 ` Tom Tromey
2009-03-27 16:36 ` Joel Brobecker
2009-03-27 16:59 ` Joel Brobecker
2009-03-27 18:47 ` Eli Zaretskii
2009-04-09 16:47 ` Tom Tromey
2009-04-09 16:59 ` Joel Brobecker
2009-04-09 17:19 ` Eli Zaretskii [this message]
2009-04-09 17:33 ` Joel Brobecker
2009-04-09 17:40 ` Eli Zaretskii
2009-04-09 20:14 ` Joel Brobecker
2009-03-31 18:31 ` Joel Brobecker
2009-03-31 20:20 ` 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=8363hd4uhq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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