Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support
Date: Thu, 29 Jan 2004 08:20:00 -0000	[thread overview]
Message-ID: <200401290820.i0T8KRZ7001876@magilla.sf.frob.com> (raw)
In-Reply-To: Eli Zaretskii's message of  , 29 January 2004 08:40:58 +0200 <u4qufl0jp.fsf@elta.co.il>

> 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


  reply	other threads:[~2004-01-29  8:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29  2:59 Roland McGrath
2004-01-29  6:39 ` Eli Zaretskii
2004-01-29  8:20   ` Roland McGrath [this message]
2004-01-29 20:14     ` Eli Zaretskii
2004-01-29 21:31       ` Roland McGrath
2004-01-30 19:03 ` Daniel Jacobowitz
2004-01-30 23:35   ` Andrew Cagney
2004-01-30 23:51     ` Roland McGrath
2004-01-31  0:11       ` Andrew Cagney
2004-01-31  0:16         ` Roland McGrath
2004-02-02 14:27           ` Andrew Cagney
2004-02-17 16:35         ` Andrew Cagney
2004-02-18  2:08           ` Roland McGrath
2004-02-24  3:50         ` Roland McGrath
2004-02-25  3:59           ` Andrew Cagney
2004-03-19  0:09             ` [COMMITTED PATCH] testsuite for info auxv Roland McGrath
2004-03-17 20:46               ` Roland McGrath
2004-02-25  4:03           ` [PATCH] auxv support Daniel Jacobowitz
2004-02-25 20:38             ` Roland McGrath
     [not found] <200401310013.i0V0DnGE018646@magilla.sf.frob.com>
2004-02-01  6:04 ` Daniel Jacobowitz
2004-02-01 22:36   ` Roland McGrath
2004-02-02  0:11   ` Roland McGrath
2004-02-02  6:24     ` Eli Zaretskii
2004-02-02 14:17   ` Andrew Cagney
2004-02-02 14:25   ` Andrew Cagney

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=200401290820.i0T8KRZ7001876@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=eliz@elta.co.il \
    --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