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:40:00 -0000 [thread overview]
Message-ID: <833ach4tj2.fsf@gnu.org> (raw)
In-Reply-To: <20090409173304.GK7535@adacore.com>
> Date: Thu, 9 Apr 2009 10:33:04 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: tromey@redhat.com, gdb-patches@sourceware.org
>
> > @xref{Thread-Specific Breakpoints}, for more about this. For
> > Ada-specific aspects, see @ref{Ada Tasks}.
>
> I agree with what you are saying, except that I think that the actual
> suggestion does not flow well with the way the paragraph is written.
> Currently, we have:
>
> It is also possible to insert a breakpoint that will stop the program
> only if a specific thread or a specific task hits that breakpoint.
> @xref{Thread-Specific Breakpoints} and @ref{Ada Tasks} for more
> information about this feature.
>
> Basically, we say: thread-specific breakpoint, or task-specific
> breakpoint. Then xref thread-specific. Then xref task-specific.
In that case, how about
It is also possible to insert a breakpoint that will stop the program
only if a specific thread or a specific task hits that breakpoint.
@xref{Thread-Specific Breakpoints}, for more information about
thread-specific breakpoints; see @ref{Ada Tasks}, for more
information about task-specific breakpoints.
or
It is also possible to insert a breakpoint that will stop the program
only if a specific thread (@pxref{Thread-Specific Breakpoints})
or a specific task (@pxref{Ada Tasks}) hits that breakpoint.
> So I propose the following in the end:
>
> It is also possible to insert a breakpoint that will stop the program
> only if a specific thread or a specific task hits that breakpoint.
> @xref{Thread-Specific Breakpoints}, and @ref{Ada Tasks}, for more
> information about this feature.
That's also OK.
next prev parent reply other threads:[~2009-04-09 17:40 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
2009-04-09 17:33 ` Joel Brobecker
2009-04-09 17:40 ` Eli Zaretskii [this message]
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=833ach4tj2.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