From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10038 invoked by alias); 26 Jan 2007 22:04:26 -0000 Received: (qmail 9977 invoked by uid 22791); 26 Jan 2007 22:04:19 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 26 Jan 2007 21:58:21 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id F232F48CDA3; Fri, 26 Jan 2007 16:58:18 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 12587-01; Fri, 26 Jan 2007 16:58:18 -0500 (EST) Received: from takamaka.act-europe.fr (joel.gnat.com [205.232.38.116]) by nile.gnat.com (Postfix) with ESMTP id BDC5148CCB8; Fri, 26 Jan 2007 16:58:18 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 1000) id 8601534C099; Sat, 27 Jan 2007 01:59:17 +0400 (RET) Date: Fri, 26 Jan 2007 22:04:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb-patches@sourceware.org Subject: Re: [RFA] new command: maintenance print target-stack Message-ID: <20070126215917.GD18453@adacore.com> References: <20070124011254.GG4667@adacore.com> <20070124200514.GA25394@nevyn.them.org> <20070125235857.GB18453@adacore.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MW5yreqqjyrRcusr" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00546.txt.bz2 --MW5yreqqjyrRcusr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 611 > 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 * gdb.texinfo (Maintenance Commands): Add documentation for the new "maint print target-stack" command. -- Joel --MW5yreqqjyrRcusr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="doco.diff" Content-length: 1130 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} --MW5yreqqjyrRcusr--