public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Pedro Alves <palves@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Improve clear command's documentation Date: Tue, 31 May 2022 14:42:34 +0000 (GMT) [thread overview] Message-ID: <20220531144234.61F7F395A014@sourceware.org> (raw) 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})}
reply other threads:[~2022-05-31 14:42 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220531144234.61F7F395A014@sourceware.org \ --to=palves@sourceware.org \ --cc=gdb-cvs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).