New "info auxv" command and $auxv variable?

[Andrew Cagney]

> Yep.
>> 
> 
>> >I think $entrypoint is more useful than $auxv.  Should we have a
>> >reserved namespace for these things?
> 
>> 
>> Ah, that.  Ref: Replace $fp with $frame / $gdbframe / $gdb.frame
>> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=327
>> 
>> Never been a decision.  $ variables are reserved for both builtins and 
>> registers but the two overlap.  Ok, here's something warped:
>> 
>> 	$.auxv
>> 
>> (i.e., "dollar dot auxv" so you know I didn't make a typo :-)
> 
> 
> Eek?  I'd prefer $gdb.auxv or $_auxv.

There is always the chance that some architecture has a register called 
"gdb".  Don't laugh, there's already a "gdt" register that's too close 
for comfort :-(

Looking at the doco:

> @cindex @code{$}
> @cindex @code{$$}
> @cindex history number
> The values printed are given @dfn{history numbers} by which you can
> refer to them.  These are successive integers starting with one.
> @code{print} shows you the history number assigned to a value by
> printing @samp{$@var{num} = } before the value; here @var{num} is the
> history number.
> 
> To refer to any previous value, use @samp{$} followed by the value's
> history number.  The way @code{print} labels its output is designed to
> remind you of this.  Just @code{$} refers to the most recent value in
> the history, and @code{$$} refers to the value before that.
> @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2}
> is the value just prior to @code{$$}, @code{$$1} is equivalent to
> @code{$$}, and @code{$$0} is equivalent to @code{$}.

So "$.frame" won't work. (=== "$$0.frame" === "<history-value>.frame") 
-> your safe :-)

So its' looking somewhat bleakly like $_frame :-)

Andrew