From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: RFA: don't repeat `delete' command
Date: Mon, 24 Jun 2002 13:46:00 -0000 [thread overview]
Message-ID: <87ptygjsu8.fsf@fleche.redhat.com> (raw)
Right now the `delete' command will repeat if you hit enter again
after it completes. Then it proceeds to give an error message, since
you've already deleted the breakpoints in question.
I've run across this by accident a few times recently. It seems a bit
odd to me, and I'd prefer that the `delete' command not repeat. Hence
this patch.
Ok?
Tom
Index: ChangeLog
from Tom Tromey <tromey@redhat.com>
* breakpoint.c (delete_command): Don't repeat `delete' commands.
Index: breakpoint.c
===================================================================
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.77
diff -u -r1.77 breakpoint.c
--- breakpoint.c 18 Jun 2002 21:58:55 -0000 1.77
+++ breakpoint.c 24 Jun 2002 20:43:14 -0000
@@ -6769,6 +6769,8 @@
{
struct breakpoint *b, *temp;
+ dont_repeat ();
+
if (arg == 0)
{
int breaks_to_delete = 0;
next reply other threads:[~2002-06-24 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 13:46 Tom Tromey [this message]
2002-06-25 19:37 ` Andrew Cagney
2002-06-25 22:23 ` Tom Tromey
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=87ptygjsu8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sources.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