From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19752 invoked by alias); 5 Nov 2003 06:12:55 -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 19745 invoked from network); 5 Nov 2003 06:12:54 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 5 Nov 2003 06:12:54 -0000 Received: from [207.232.27.5] (helo=WST0054) by monty-python.gnu.org with asmtp (Exim 4.24) id 1AHGsJ-0006kX-CN; Wed, 05 Nov 2003 01:10:39 -0500 Date: Wed, 05 Nov 2003 06:12:00 -0000 Message-Id: From: Eli Zaretskii To: Andrew Cagney CC: gdb@sources.redhat.com In-reply-to: <3FA7D7C8.50609@redhat.com> (message from Andrew Cagney on Tue, 04 Nov 2003 11:46:00 -0500) Subject: Re: New "info auxv" command and $auxv variable? Reply-to: Eli Zaretskii References: <3FA7D7C8.50609@redhat.com> X-SW-Source: 2003-11/txt/msg00034.txt.bz2 > Date: Tue, 04 Nov 2003 11:46:00 -0500 > From: Andrew Cagney > > (gdb) info auxv > Entry point 0x1234 > ... > (gdb) > > that listed the contents of the processes auxv table. > > 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? Yes, please!