From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25377 invoked by alias); 29 Jan 2004 08:20:34 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 25256 invoked from network); 29 Jan 2004 08:20:31 -0000 Received: from unknown (HELO gateway.sf.frob.com) (64.81.54.130) by sources.redhat.com with SMTP; 29 Jan 2004 08:20:31 -0000 Received: from magilla.sf.frob.com (magilla.sf.frob.com [198.49.250.228]) by gateway.sf.frob.com (Postfix) with ESMTP id A104E357B; Thu, 29 Jan 2004 00:20:30 -0800 (PST) Received: from magilla.sf.frob.com (localhost.localdomain [127.0.0.1]) by magilla.sf.frob.com (8.12.9/8.12.9) with ESMTP id i0T8KTOi001881; Thu, 29 Jan 2004 00:20:29 -0800 Received: (from roland@localhost) by magilla.sf.frob.com (8.12.9/8.12.9/Submit) id i0T8KRZ7001876; Thu, 29 Jan 2004 00:20:27 -0800 Date: Thu, 29 Jan 2004 08:20:00 -0000 Message-Id: <200401290820.i0T8KRZ7001876@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] auxv support In-Reply-To: Eli Zaretskii's message of , 29 January 2004 08:40:58 +0200 X-Antipastobozoticataclysm: Bariumenemanilow X-SW-Source: 2004-01/txt/msg00737.txt.bz2 > I'd like to see the manual changed to described `info auxv'. Where does the description belong? I tried to follow the model of `info udot' and `info dcache', which seem similar in general flavor of topic. But these I cannot find documented anywhere. `info proc' is documented in a subsection of `Native'. That does not seem appropriate, since `info auxv' works on target core files regardless of host, and probably soon will work for remote targets. As written, the `info auxv' is available in all configurations, just only ever succeeds for certain targets. So it doesn't seem like it belongs under @chapter Configuration-Specific Information at all. Perhaps it should just be a new section in @chapter Examining Data? How about this? --- gdb.texinfo.~1.190.~ 2004-01-28 16:21:23.000000000 -0800 +++ gdb.texinfo 2004-01-29 00:20:19.000000000 -0800 @@ -4684,6 +4684,7 @@ Table}. * Registers:: Registers * Floating Point Hardware:: Floating point hardware * Vector Unit:: Vector Unit +* Auxiliary Vector:: Auxiliary data provided by operating system * Memory Region Attributes:: Memory region attributes * Dump/Restore Files:: Copy between memory and a file * Character Sets:: Debugging programs that use a different @@ -5864,6 +5865,32 @@ Display information about the vector uni layout vary depending on the hardware. @end table +@node Auxiliary Vector +@section Operating system auxiliary vector +@cindex auxiliary vector +@cindex vector, auxiliary + +Some operating systems supply an @dfn{auxiliary vector} to programs at +startup. This is akin to the arguments and environment that you +specify for a program, but contains a system-dependent variety of +binary values that tell system libraries important details about the +hardware, operating system, and process. Each value's purpose is +identified by an integer tag; the meanings are well-known but system-specific. +Depending on the configuration and operating system facilities, +@value{GDBN} may be able to show you this information. + +@table @code +@kindex info auxv +@item info auxv +Display the auxiliary vector of the inferior, which can be either a +live process or a core dump file. @{GDBN} prints each tag value +numerically, and also shows names and text descriptions for recognized +tags. Some values in the vector are numbers, some bit masks, and some +pointers to strings or other data. @{GDBN} displays each value in the +most appropriate form for a recognized tag, and in hexadecimal for +an unrecognized tag. +@end table + @node Memory Region Attributes @section Memory region attributes @cindex memory region attributes