From: Vladimir Prus <ghost@cs.msu.su>
To: Bogdan Slusarczyk <bodzio131@op.pl>
Cc: gdb@sources.redhat.com
Subject: Re: tracing variables - is it ok?
Date: Fri, 01 Jun 2007 09:17:00 -0000 [thread overview]
Message-ID: <200706011317.39198.ghost@cs.msu.su> (raw)
In-Reply-To: <465FE337.9020704@op.pl>
On Friday 01 June 2007 13:13, Bogdan Slusarczyk wrote:
> Vladimir Prus pisze:
> > This seems weird. Can you also print 'a' right after creating varobj,
> > and right after -var-update, to make sure it's the problem with
> > variable objects, and not with something else. Please do this test with
> > gdb 6.6, or better yet, with CVS version.
> I did -var-evaluate-expression just after creating varobj and I got
> proper value (testA, a=10 ). After -var-update (in testB) value is not
> changed. I did this test with gdb 6.6.
Please do "print a". The -var-evaluate-expression won't show changed
value if -var-update did not mention a given variable object.
- Volodya
next prev parent reply other threads:[~2007-06-01 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 7:59 Bogdan Slusarczyk
2007-06-01 8:37 ` Vladimir Prus
2007-06-01 9:13 ` Bogdan Slusarczyk
2007-06-01 9:17 ` Vladimir Prus [this message]
2007-06-01 9:28 ` Bogdan Slusarczyk
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=200706011317.39198.ghost@cs.msu.su \
--to=ghost@cs.msu.su \
--cc=bodzio131@op.pl \
--cc=gdb@sources.redhat.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