From: Jim Blandy <jimb@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: RFA: Document @-frame variable objects
Date: Fri, 25 May 2007 17:59:00 -0000 [thread overview]
Message-ID: <m3tzu095cm.fsf@codesourcery.com> (raw)
Could the MI folks also read this over for accuracy?
gdb/doc/ChangeLog:
2007-05-25 Jim Blandy <jimb@codesourcery.com>
* gdb.texinfo (GDB/MI Variable Objects): Document @-frame variable
objects.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.405
diff -u -r1.405 gdb.texinfo
--- gdb/doc/gdb.texinfo 16 May 2007 14:16:32 -0000 1.405
+++ gdb/doc/gdb.texinfo 25 May 2007 17:31:14 -0000
@@ -19250,7 +19250,7 @@
@smallexample
-var-create @{@var{name} | "-"@}
- @{@var{frame-addr} | "*"@} @var{expression}
+ @{@var{frame-addr} | "*" | "@@"@} @var{expression}
@end smallexample
This operation creates a variable object, which allows the monitoring of
@@ -19263,12 +19263,33 @@
unique provided that one does not specify @var{name} on that format.
The command fails if a duplicate name is found.
-The frame under which the expression should be evaluated can be
-specified by @var{frame-addr}. A @samp{*} indicates that the current
-frame should be used.
+The second argument indicates the scope in which GDB should evaluate
+@var{expression}:
+@itemize @bullet
+@item
+If it is @var{frame-addr}, then GDB finds a frame at that address in
+the current stack, and evaluates @var{expression} in that frame's
+scope. When the frame is eventually popped, the variable object is
+marked out of scope.
+
+@item
+If it is @samp{*}, then GDB evaluates @var{expression} in the scope of
+the frame selected at the time the @code{-var-create} command is
+given. When the frame is eventually popped, the variable object is
+marked out of scope.
+
+@item
+If it is @samp{@@}, then the expression has no fixed scope: GDB
+evaluates @var{expression} in the currently selected frame, and future
+@code{-var-update} commands will use whatever frame is selected when
+they are invoked. Variable objects of this sort may go in and out of
+scope as the program runs, and their type may change from one update
+to the next.
+
+@end itemize
-@var{expression} is any expression valid on the current language set (must not
-begin with a @samp{*}), or one of the following:
+@var{expression} is any expression valid on the current language set
+(although it must not begin with a @samp{*}), or one of the following:
@itemize @bullet
@item
next reply other threads:[~2007-05-25 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 17:59 Jim Blandy [this message]
2007-05-25 19:08 ` Eli Zaretskii
2007-05-26 0:42 ` Nick Roberts
2007-05-26 5:53 ` Nick Roberts
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=m3tzu095cm.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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