Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Document task-specific breakpoints
Date: Thu, 09 Apr 2009 20:14:00 -0000	[thread overview]
Message-ID: <20090409201437.GL7535@adacore.com> (raw)
In-Reply-To: <833ach4tj2.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

>      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.

I like this suggestion best, so this is what I checked in. Thanks
a lot!

2009-04-09  Joel Brobecker  <brobecker@adacore.com>

        * gdb.texinfo (Set Breaks): Rewrite a paragraph to avoid a warning
        about a missing dot or coma after @xref.

-- 
Joel

[-- Attachment #2: doc.diff --]
[-- Type: text/x-diff, Size: 810 bytes --]

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.578
diff -u -p -r1.578 gdb.texinfo
--- gdb.texinfo	2 Apr 2009 15:56:08 -0000	1.578
+++ gdb.texinfo	9 Apr 2009 20:10:18 -0000
@@ -3052,9 +3052,8 @@ C@t{++}, a function name may refer to mo
 that situation.
 
 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.
+only if a specific thread (@pxref{Thread-Specific Breakpoints})
+or a specific task (@pxref{Ada Tasks}) hits that breakpoint.
 
 @item break
 When called without any arguments, @code{break} sets a breakpoint at

  reply	other threads:[~2009-04-09 20:14 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
2009-04-09 20:14                 ` Joel Brobecker [this message]
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=20090409201437.GL7535@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --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