public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
* [binutils-gdb] Improve clear command's documentation
@ 2022-05-31 14:42 Pedro Alves
  0 siblings, 0 replies; only message in thread
From: Pedro Alves @ 2022-05-31 14:42 UTC (permalink / raw)
  To: gdb-cvs

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=622c4842bb451efd519c32312c2372f472cd99c8

commit 622c4842bb451efd519c32312c2372f472cd99c8
Author: Pedro Alves <pedro@palves.net>
Date:   Tue May 31 10:54:17 2022 +0100

    Improve clear command's documentation
    
    Co-Authored-By: Eli Zaretskii <eliz@gnu.org>
    
    Change-Id: I9440052fd28f795d6f7c93a4576beadd21f28885

Diff:
---
 gdb/doc/gdb.texinfo | 35 +++++++++++++++++++++++++----------
 1 file changed, 25 insertions(+), 10 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index f94df686bab..5f09f3a1433 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -5443,21 +5443,36 @@ the innermost frame is selected, this is a good way to delete a
 breakpoint where your program just stopped.
 
 @item clear @var{locspec}
-Delete breakpoints with code locations that match @var{locspec}.
-@xref{Location Specifications}, for the various forms of
-@var{locspec}; the most useful ones are listed below:
+Delete any breakpoint with a code location that corresponds to
+@var{locspec}.  @xref{Location Specifications}, for the various forms
+of @var{locspec}.  Which code locations correspond to @var{locspec}
+depends on the form used in the location specification @var{locspec}:
 
 @table @code
-@item clear @var{function}
-@itemx clear @var{filename}:@var{function}
-Delete any breakpoints set at entry to the named @var{function}.
+@item @var{linenum}
+@itemx @var{filename}:@var{linenum}
+@itemx -line @var{linenum}
+@itemx -source @var{filename} -line @var{linenum}
+If @var{locspec} specifies a line number, with or without a file name,
+the command deletes any breakpoint with a code location that is at or
+within the specified line @var{linenum} in files that match the
+specified @var{filename}.  If @var{filename} is omitted, it defaults
+to the current source file.
+
+@item *@var{address}
+If @var{locspec} specifies an address, the command deletes any
+breakpoint with a code location that is at the given @var{address}.
 
-@item clear @var{linenum}
-@itemx clear @var{filename}:@var{linenum}
-Delete any breakpoints set at or within the code of the specified
-@var{linenum} of the specified @var{filename}.
+@item @var{function}
+@itemx -function @var{function}
+If @var{locspec} specifies a function, the command deletes any
+breakpoint with a code location that is at the entry to any function
+whose name matches @var{function}.
 @end table
 
+Ambiguity in names of files and functions can be resolved as described
+in @ref{Location Specifications}.
+
 @cindex delete breakpoints
 @kindex delete
 @kindex d @r{(@code{delete})}


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-05-31 14:42 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-31 14:42 [binutils-gdb] Improve clear command's documentation Pedro Alves

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).