From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com, Vladimir Prus <ghost@cs.msu.su>
Subject: Re: [PATCH] -var-update [was Re: Variable objects: references formatting]
Date: Wed, 17 May 2006 01:43:00 -0000 [thread overview]
Message-ID: <17515.52645.132594.285414@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060517004527.GA19347@nevyn.them.org>
> > > Every time my_value_equal is called its first argument comes from a
> > > varobj's ->value. It seems to me that if we want to properly know
> > > whether the varobj has changed, we'd better have read its value into
> > > GDB.
> >
> > Could it not doing that because GDB's value mechanism isn't working
> > properly for references?
>
> The value mechanism is working fine; it's varobj that does not support
> references.
Well GDB appears to interpret the address as being the value, its actual value
doesn't seem to be stored in the value structure (or if it is, I can't find
it).
When the actual value gets printed it seems to come out of smething like
print_address_demangle.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-05-17 1:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 23:05 Variable objects: references formatting Nick Roberts
2006-05-03 23:50 ` Jim Blandy
2006-05-04 1:53 ` Nick Roberts
2006-05-04 17:32 ` Jim Blandy
2006-05-04 22:30 ` Nick Roberts
2006-05-05 8:08 ` Jim Blandy
2006-05-04 5:30 ` Vladimir Prus
2006-05-04 6:21 ` Nick Roberts
2006-05-04 7:00 ` Vladimir Prus
2006-05-04 7:20 ` Nick Roberts
2006-05-04 12:10 ` Vladimir Prus
2006-05-08 12:41 ` [PATCH] -var-update [was Re: Variable objects: references formatting] Nick Roberts
2006-05-08 17:27 ` Jim Blandy
2006-05-08 21:17 ` Nick Roberts
2006-05-15 16:54 ` Daniel Jacobowitz
2006-05-17 0:45 ` Nick Roberts
2006-05-17 1:28 ` Daniel Jacobowitz
2006-05-17 1:43 ` Nick Roberts [this message]
2006-05-17 3:39 ` Daniel Jacobowitz
2006-05-19 7:41 ` [PATCH] -var-update Nick Roberts
2006-05-19 9:47 ` Vladimir Prus
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=17515.52645.132594.285414@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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