Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <ghost@cs.msu.su>
To: Jim Ingham <jingham@apple.com>
Cc: Nick Roberts <nickrob@snap.net.nz>,
	 Daniel Jacobowitz <drow@false.org>,
	 gdb@sources.redhat.com
Subject: Re: -var-update and address changes
Date: Wed, 03 May 2006 06:03:00 -0000	[thread overview]
Message-ID: <200605031002.21910.ghost@cs.msu.su> (raw)
In-Reply-To: <1B177ECC-2AD9-4476-AF44-D91F4268E70E@apple.com>

On Tuesday 02 May 2006 21:22, Jim Ingham wrote:
> Shouldn't the call to var->root->lang->value_of_root down at the
> bottom of value_of_root take care of fetching the new value?  

Well, it fetches the new value, I believe.

> You 
> don't want to discard the old varobj unless you have to, because if
> the varobj represents a structure or pointer to a structure and the
> user has fetched any children, or changed the format, or whatever,
> you will lose that state.

Ah, that's right. In fact much of complexity in current KDevelop code is 
maintaining open/close state of items, so would be nice if gdb handled this.
Do you suggest that we don't create new varobj unless value change, or that we 
carry over all settings from the old one to the new?

>
> Also, I must be missing something this morning, but I can't see any
> difference between your two examples.

Ah, sorry, they are the same indeed. In the second example, the type of 'i' 
inside 'foo' function should be 'int'. In that case, gdb does not notice that 
name 'i' now refers to different variable.

- Volodya


  reply	other threads:[~2006-05-03  6:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 16:02 Vladimir Prus
2006-04-12 18:25 ` Jim Ingham
2006-04-13  9:25   ` Vladimir Prus
2006-04-13 17:31     ` Jim Ingham
2006-04-14 13:25   ` Daniel Jacobowitz
2006-04-14 20:03     ` Jim Ingham
2006-04-14 20:09       ` Daniel Jacobowitz
2006-04-14 20:27         ` Jim Ingham
2006-04-14 21:37           ` Daniel Jacobowitz
2006-04-17  6:18             ` Vladimir Prus
2006-04-17  9:02               ` Mark Kettenis
2006-04-17 10:54                 ` Vladimir Prus
2006-05-02 12:50       ` Vladimir Prus
2006-05-02 13:14         ` Nick Roberts
2006-05-02 13:41           ` Vladimir Prus
2006-05-02 17:23             ` Jim Ingham
2006-05-03  6:03               ` Vladimir Prus [this message]
     [not found]                 ` <20060504145046.GA32605@nevyn.them.org>
2006-05-04 15:12                   ` Vladimir Prus
2006-05-04 15:13                     ` Daniel Jacobowitz
2006-05-05  6:25                   ` Vladimir Prus
2006-05-05 15:02                     ` Daniel Jacobowitz
2006-04-16 15:52     ` 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=200605031002.21910.ghost@cs.msu.su \
    --to=ghost@cs.msu.su \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.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