From 2c88c651a411e02bf9e238c73211112f86c95ef1 Mon Sep 17 00:00:00 2001 From: Joel Brobecker Date: Thu, 9 Apr 2009 20:11:57 +0000 Subject: [PATCH] * gdb.texinfo (Set Breaks): Rewrite a paragraph to avoid a warning about a missing dot or coma after @xref. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 5 ++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 8678d982418..b70d85c9394 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2009-04-09 Joel Brobecker + + * gdb.texinfo (Set Breaks): Rewrite a paragraph to avoid a warning + about a missing dot or coma after @xref. + 2009-04-02 Joel Brobecker * gdb.texinfo (Backtrace): Add a parameter in frame 1 of the first diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f4aa21d4fef..5269dfcfc93 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -3052,9 +3052,8 @@ C@t{++}, a function name may refer to more than one possible place to break. 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 -- 2.30.2