From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: [RFC/RFA] new command: maintenance print target-stack
Date: Tue, 17 Oct 2006 22:52:00 -0000 [thread overview]
Message-ID: <20061017225247.GQ1903@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hello,
While working to "auto-solib-add", I found that I was very frequently
in need to dumping the current target stack (I just need the names),
to see if the multi-thread layer has been pushed or not. So I
implemented a new "maintenance" command, hoping that others might
find it useful.
(gdb) maintenance print target-stack
The current target stack is:
- multi-thread (multi-threaded child process.)
- child (Unix child process)
- exec (Local exec file)
- None (None)
Opinions? Eventually, we might want to actually dump more
information if that's useful to others, but that's a start.
2006-10-17 Joel Brobecker <brobecker@adacore.com>
* target.c (maintenance_print_target_stack): New function.
(initialize_targets): Add new "maintenance print target-stack"
command.
Tested on x86-linux just to make sure, no regression. I will of course
provide documentation for this if the idea is accepted.
--
Joel
[-- Attachment #2: target.c.diff --]
[-- Type: text/plain, Size: 1188 bytes --]
Index: target.c
===================================================================
RCS file: /cvs/src/src/gdb/target.c,v
retrieving revision 1.127
diff -u -p -r1.127 target.c
--- target.c 10 Oct 2006 03:17:53 -0000 1.127
+++ target.c 17 Oct 2006 22:41:16 -0000
@@ -2689,6 +2689,21 @@ do_monitor_command (char *cmd,
target_rcmd (cmd, gdb_stdtarg);
}
+/* Print the name of each layers of our target stack. */
+
+static void
+maintenance_print_target_stack (char *cmd, int from_tty)
+{
+ struct target_ops *t;
+
+ printf_filtered (_("The current target stack is:\n"));
+
+ for (t = target_stack; t != NULL; t = t->beneath)
+ {
+ printf_filtered (" - %s (%s)\n", t->to_shortname, t->to_longname);
+ }
+}
+
void
initialize_targets (void)
{
@@ -2722,5 +2737,9 @@ result in significant performance improv
add_com ("monitor", class_obscure, do_monitor_command,
_("Send a command to the remote monitor (remote targets only)."));
+ add_cmd ("target-stack", class_maintenance, maintenance_print_target_stack,
+ _("Print the name of each layer of the internal target stack."),
+ &maintenanceprintlist);
+
target_dcache = dcache_init ();
}
next reply other threads:[~2006-10-17 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 22:52 Joel Brobecker [this message]
2006-10-20 17:01 ` Kevin Buettner
2006-10-22 20:03 ` Mark Kettenis
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=20061017225247.GQ1903@adacore.com \
--to=brobecker@adacore.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