Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: New "info auxv" command and $auxv variable?
Date: Tue, 04 Nov 2003 16:55:00 -0000	[thread overview]
Message-ID: <20031104165525.GA2599@nevyn.them.org> (raw)
In-Reply-To: <3FA7D7C8.50609@redhat.com>

On Tue, Nov 04, 2003 at 11:46:00AM -0500, Andrew Cagney wrote:
> Hello,
> 
> In implementing a mechanism to query values from the the target's AUXV 
> (/proc/$$/auxv) I decided I might as well add a generic command:
> 
> 	(gdb) info auxv
> 	Entry point 0x1234
> 	...
> 	(gdb)
> 
> that listed the contents of the processes auxv table.

This would be useful.

> 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).

> PS: Can any one point me at an official GNU/Linux or, I guess *BSD, 
> distro that supports /proc/$$/auxv?  So far I've only got Solaris :-/

There aren't any released distros that do, as far as I know.  You'd
have to run a 2.6.0-test9 kernel.  Unless RH has backported it to their
2.4 patches?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-11-04 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 16:46 Andrew Cagney
2003-11-04 16:55 ` Daniel Jacobowitz [this message]
2003-11-04 19:59   ` Andrew Cagney
2003-11-04 20:02     ` Daniel Jacobowitz
2003-11-04 20:15       ` Andrew Cagney
2003-11-04 20:17         ` Daniel Jacobowitz
2003-11-04 20:39           ` Andrew Cagney
2003-11-05  6:12 ` Eli Zaretskii

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=20031104165525.GA2599@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@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