Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: New "info auxv" command and $auxv variable?
Date: Tue, 04 Nov 2003 20:17:00 -0000	[thread overview]
Message-ID: <20031104201728.GA10060@nevyn.them.org> (raw)
In-Reply-To: <3FA808CC.4030201@redhat.com>

On Tue, Nov 04, 2003 at 03:15:08PM -0500, Andrew Cagney wrote:
> >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?
> >
> >
> >Oops, I misread you.  The MI command is definitely a good idea -
> >"-info-auxv", right?
> 
> 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.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-11-04 20:17 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
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 [this message]
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=20031104201728.GA10060@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.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