From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] new command: maintenance print target-stack
Date: Fri, 26 Jan 2007 22:04:00 -0000 [thread overview]
Message-ID: <20070126215917.GD18453@adacore.com> (raw)
In-Reply-To: <usldyb04m.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
> This is okay, except that the term "target stack", and what is pushed
> onto it, is not explained anywhere in the manual, not even in
> gdbint.texinfo. Can you add a sentence or two saying what it is?
>
> Also, the first usage of "target stack" should be in @dfn, which is
> our way of saying that this is a new term.
Good points. I was lucky to find something in target.h, so I shamelessly
copied it. How does this look?
2007-01-26 Joel Brobecker <brobecker@adacore.com>
* gdb.texinfo (Maintenance Commands): Add documentation for
the new "maint print target-stack" command.
--
Joel
[-- Attachment #2: doco.diff --]
[-- Type: text/plain, Size: 1130 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.379
diff -u -p -r1.379 gdb.texinfo
--- gdb.texinfo 20 Jan 2007 16:51:55 -0000 1.379
+++ gdb.texinfo 26 Jan 2007 21:55:27 -0000
@@ -22667,6 +22667,19 @@ average, and median entry size, total me
savings, and various measures of the hash table size and chain
lengths.
+@kindex maint print target-stack
+@cindex target stack description
+@item maint print target-stack
+A @dfn{target} is an interface between the debugger and a particular
+kind of file or process. Targets can be stacked in @dfn{strata},
+so that more than one target can potentially respond to a request.
+In particular, memory accesses will walk down the stack of targets
+until they find a target that is interested in handling that particular
+address.
+
+This command prints a short description of each layer that was pushed on
+the @dfn{target stack}, starting from the top layer down to the bottom one.
+
@kindex maint print type
@cindex type chain of a data type
@item maint print type @var{expr}
next prev parent reply other threads:[~2007-01-26 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 1:13 Joel Brobecker
2007-01-24 4:19 ` Eli Zaretskii
2007-01-24 16:19 ` Joel Brobecker
2007-01-24 19:50 ` Eli Zaretskii
2007-01-24 20:03 ` Joel Brobecker
2007-01-24 20:05 ` Daniel Jacobowitz
2007-01-25 23:58 ` Joel Brobecker
2007-01-26 9:36 ` Eli Zaretskii
2007-01-26 22:04 ` Joel Brobecker [this message]
2007-01-27 10:33 ` Eli Zaretskii
2007-01-29 16:38 ` Joel Brobecker
2007-01-29 16:38 ` Joel Brobecker
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=20070126215917.GD18453@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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