From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5016 invoked by alias); 4 Nov 2003 20:39:03 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5008 invoked from network); 4 Nov 2003 20:39:02 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 4 Nov 2003 20:39:02 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 3D1F12B8F; Tue, 4 Nov 2003 15:38:58 -0500 (EST) Message-ID: <3FA80E62.30805@redhat.com> Date: Tue, 04 Nov 2003 20:39:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com Subject: Re: New "info auxv" command and $auxv variable? References: <3FA7D7C8.50609@redhat.com> <20031104165525.GA2599@nevyn.them.org> <3FA80508.6030601@redhat.com> <20031104200243.GA9441@nevyn.them.org> <3FA808CC.4030201@redhat.com> <20031104201728.GA10060@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00031.txt.bz2 > 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" === ".frame") -> your safe :-) So its' looking somewhat bleakly like $_frame :-) Andrew