From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>, Eli Zaretskii <eliz@gnu.org>,
"tromey@redhat.com" <tromey@redhat.com>,
"guillaume.leconte@gmail.com" <guillaume.leconte@gmail.com>
Subject: Re: [patch] delete a range of display numbers
Date: Fri, 18 Feb 2011 18:06:00 -0000 [thread overview]
Message-ID: <201102181756.52921.pedro@codesourcery.com> (raw)
In-Reply-To: <4D5EB239.7050508@vmware.com>
On Friday 18 February 2011 17:54:01, Michael Snyder wrote:
> delete [breakpoints] [range...]
> Delete the breakpoints, watchpoints, or catchpoints of the
> breakpoint ranges specified as arguments. If no argument is specified,
> delete all breakpoints (gdb asks confirmation, unless you have set
> confirm off). You can abbreviate this command as d.
I need new glasses. Thanks!
The help text could use an update though:
(gdb) help delete breakpoints
Delete some breakpoints or auto-display expressions.
Arguments are breakpoint numbers with spaces in between.
To delete all breakpoints, give no argument.
This command may be abbreviated "delete".
--
Pedro Alves
next prev parent reply other threads:[~2011-02-18 17:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 9:47 Guillaume Leconte
2011-02-18 10:30 ` Guillaume Leconte
2011-02-18 11:08 ` Eli Zaretskii
2011-02-18 11:48 ` Guillaume Leconte
2011-02-18 12:17 ` Pedro Alves
2011-02-18 14:41 ` Guillaume Leconte
2011-02-18 15:14 ` Tom Tromey
2011-02-18 15:58 ` Pedro Alves
2011-02-18 16:48 ` Tom Tromey
2011-02-18 16:57 ` Pedro Alves
2011-02-18 17:41 ` Eli Zaretskii
2011-02-18 17:54 ` Pedro Alves
2011-02-18 17:54 ` Michael Snyder
2011-02-18 18:06 ` Pedro Alves [this message]
2011-03-14 21:24 ` [patch+docs] make 'disable|enable display' also accept ranges (Re: [patch] delete a range of display numbers) Pedro Alves
2011-03-14 21:34 ` Eli Zaretskii
2011-03-15 14:43 ` Pedro Alves
2011-02-18 18:17 ` [patch] delete a range of display numbers Eli Zaretskii
2011-02-18 17:52 ` Michael Snyder
2011-02-18 17:57 ` Pedro Alves
2011-02-18 17:44 ` Michael Snyder
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=201102181756.52921.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=guillaume.leconte@gmail.com \
--cc=msnyder@vmware.com \
--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