From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17465 invoked by alias); 4 Nov 2003 19:59:09 -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 17458 invoked from network); 4 Nov 2003 19:59:09 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 4 Nov 2003 19:59:09 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DDF4F2B8F; Tue, 4 Nov 2003 14:59:04 -0500 (EST) Message-ID: <3FA80508.6030601@redhat.com> Date: Tue, 04 Nov 2003 19:59: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> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00027.txt.bz2 > But why stop there? What about a builtin $auxv variable, a struct, vis: >> >> (gdb) print $auxv >> $1 = { entry = 0x1234, ... } >> >> Oh, and I guess: >> >> (gdb) interpreter mi --info-auxv >> ^ok,result={entry="0x1234",...} >> >> Thoughts? > > > I don't know if there's enough utility to bother doing this, though... > the only thing likely to be generally useful is the entry point (and > maybe the vsyscall address). If we start making the CLI more usable by making this stuff available people might start using it :-) Anyway, the MI stuff is almost free (the code is common). The $auxv variable is a bit tricky but still ok. Could just add $entrypoint? Andrew