From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: tracing variables - is it ok?
Date: Fri, 01 Jun 2007 08:37:00 -0000 [thread overview]
Message-ID: <f3ols1$gp9$1@sea.gmane.org> (raw)
In-Reply-To: <465FD1AD.9040909@op.pl>
Bogdan Slusarczyk wrote:
> Hi everybody, suppose such code:
>
> void testB( int a ) { //a == 20
> int k = a;
> }
> void testA( int a ) { //a == 10
> int k = a;
> testB( 20 );
> }
> void main() {
> testA( 10 );
> }
>
> Inside testA I did '-var-create - @ a' and inside testB '-var-update',
> but gdb (6.3, 6.6) says that nothing changes and returns a==10 from
> testA.
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.
Thanks,
Volodya
next prev parent reply other threads:[~2007-06-01 8:37 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 [this message]
2007-06-01 9:13 ` Bogdan Slusarczyk
2007-06-01 9:17 ` Vladimir Prus
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='f3ols1$gp9$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--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