Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Daniel Jacobowitz <drow@false.org>,  gdb-patches@sources.redhat.com
Subject: Re: [mi] [ada] varobjs for registers 2
Date: Fri, 05 Jan 2007 10:47:00 -0000	[thread overview]
Message-ID: <200701051346.59389.ghost@cs.msu.su> (raw)
In-Reply-To: <17822.10079.540550.7046@kahikatea.snap.net.nz>

On Friday 05 January 2007 13:24, Nick Roberts wrote:
>  > +@smallexample
>  > + -var-list --@var{kind} @{@var{frame-addr} | "*"@}
>  > +@end smallexample
>  > +
>  >...
>  > +
>  > +At the moment the only defined kind is ``registers''. 
> 
> Isn't "-var-list --registers" only meaningful with USE_SELECTED_FRAME
> i.e "-var-list --registers @"?

It can be also meanigful with specific frame number.

> Likewise "-var-list --locals" generally would only make seem to make sense
> with USE_CURRENT_FRAME i.e "-var-list --locals *".

For --local, I expect it to be meaningful only with specific frame number. Anyway, such
meaningfullness specific to each kind can be documented separately. I'm not sure
the general syntax need those details.

> Also, looking ahead, I wonder what Apple do about deleting variable objects for
> locals when the program exits the frame.  Perhaps "-var-list --locals" should
> delete them.

Oh, I guess I really should post my ideas about this. In on my todo for today.

- Volodya


      reply	other threads:[~2007-01-05 10:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 18:38 Vladimir Prus
2006-12-20 19:44 ` Eli Zaretskii
2007-01-05  9:01   ` Vladimir Prus
2007-01-05  9:29     ` Eli Zaretskii
2006-12-21  7:20 ` Joel Brobecker
2006-12-30 20:30   ` Daniel Jacobowitz
2007-01-05  9:06     ` Vladimir Prus
2007-01-05 10:24       ` Nick Roberts
2007-01-05 10:47         ` Vladimir Prus [this message]

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=200701051346.59389.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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