From: sbaugh@catern.com
To: gdb-patches@sourceware.org
Subject: [PATCH] gdb: add -a option for remove-inferior
Date: Thu, 29 Dec 2016 17:45:00 -0000 [thread overview]
Message-ID: <87a8bebqug.fsf@catern.com> (raw)
I find myself frequently wanting to wipe out the current set of
inferiors: detaching from all of them, or killing them all, and then
starting anew. A -a flag to the various inferior commands which currently
just take ranges of ids would make this a lot easier. Does that sound
like a reasonable enhancement?
If this patch is acceptable I'll go ahead and add -a flags like this to
all the inferior commands where it makes sense, and add docs, and
resubmit.
This adds a -a option for remove-inferior; when passed, all inferiors
will be removed.
---
gdb/inferior.c | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
diff --git a/gdb/inferior.c b/gdb/inferior.c
index 32b6db2..f4cd062 100644
--- a/gdb/inferior.c
+++ b/gdb/inferior.c
@@ -775,13 +775,25 @@ info_inferiors_command (char *args, int from_tty)
print_inferior (current_uiout, args);
}
-/* remove-inferior ID */
+/* remove-inferior [-a] ID */
static void
remove_inferior_command (char *args, int from_tty)
{
if (args == NULL || *args == '\0')
- error (_("Requires an argument (inferior id(s) to remove)"));
+ error (_("Requires an argument (inferior id(s) to remove or -a)"));
+
+ if (startswith (args, "-a"))
+ {
+ struct inferior *inf, *cur;
+ cur = current_inferior();
+ ALL_INFERIORS(inf)
+ {
+ if (inf != cur)
+ delete_inferior (inf);
+ }
+ return;
+ }
number_or_range_parser parser (args);
while (!parser.finished ())
@@ -1056,7 +1068,7 @@ as main program."));
add_com ("remove-inferiors", no_class, remove_inferior_command, _("\
Remove inferior ID (or list of IDs).\n\
-Usage: remove-inferiors ID..."));
+Usage: remove-inferiors [-a] ID..."));
add_com ("clone-inferior", no_class, clone_inferior_command, _("\
Clone inferior ID.\n\
--
2.10.0
next reply other threads:[~2016-12-29 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 17:45 sbaugh [this message]
2016-12-29 18:13 ` Luis Machado
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=87a8bebqug.fsf@catern.com \
--to=sbaugh@catern.com \
--cc=gdb-patches@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: 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