Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Document fixed/floating variable objects and thread-id.
Date: Sat, 26 Apr 2008 18:45:00 -0000	[thread overview]
Message-ID: <uod7wzexa.fsf@gnu.org> (raw)
In-Reply-To: <fuvo0g$2rm$1@ger.gmane.org>

> From:  Vladimir Prus <vladimir@codesourcery.com>
> Date:  Sat, 26 Apr 2008 21:16:01 +0400
> 
> > More to the point, I cannot say that I have a clear understanding of
> > the issue.  In what other situations will fixed and floating varobjs
> > behave differently?  Are we talking about any situation where
> > identically named variables have different binding to memory
> > addresses, depending on scope and context?  
> 
> Yes.

Okay, thanks for explaining this to me.  Based on what you wrote, I
suggest to say ``the values of variables whose names appear in the
expressions are re-evaluated every time in the context of the current
frame.''  Adding a couple of examples might explain this even further.


  reply	other threads:[~2008-04-26 17:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04  9:32 Vladimir Prus
2008-04-04 11:47 ` Eli Zaretskii
2008-04-09 13:49   ` Vladimir Prus
2008-04-09 15:21     ` Eli Zaretskii
2008-04-09 17:06       ` Vladimir Prus
2008-04-09 18:04         ` Eli Zaretskii
2008-04-09 20:37           ` Vladimir Prus
2008-04-09 21:25             ` Eli Zaretskii
2008-04-09 22:17               ` Vladimir Prus
2008-04-23 11:52                 ` Vladimir Prus
2008-04-23 18:00                   ` Eli Zaretskii
2008-04-26 17:44                     ` Vladimir Prus
2008-04-26 18:45                       ` Eli Zaretskii [this message]
2008-04-04 13:08 ` Daniel Jacobowitz
2008-04-04 13:44 ` Pedro Alves

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=uod7wzexa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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