From: Yao Qi <yao@codesourcery.com>
To: David Taylor <dtaylor@emc.com>
Cc: <gdb@sourceware.org>
Subject: Re: trace state variables -- what should be traced?
Date: Mon, 15 Sep 2014 04:04:00 -0000 [thread overview]
Message-ID: <87iokp4joy.fsf@codesourcery.com> (raw)
In-Reply-To: <32355.1410551103@usendtaylorx2l> (David Taylor's message of "Fri, 12 Sep 2014 15:45:03 -0400")
David Taylor <dtaylor@emc.com> writes:
> variables, it can be set with an aop_setv operation. Which value should
> be recorded?
>
> The old value? Or the new value?
I prefer both.
>
> Currently the new value is always recorded and sometimes the old value
> is recorded as well.
Do you have an example that old value is *not* recorded?
>
> Since the old value, when it is recorded, is always recorded prior to
> recording the new value, the new value overwrites the old value.
The old value and the new value are recorded in the different 'V' blocks
of the traceframe, so the new value shouldn't overwrite the old value.
There was a bug in GDB that it reads the first matched tsv, so the old value
of this tsv may be read, but this bug was fixed by reading last matched
tsv <https://sourceware.org/ml/gdb-patches/2013-03/msg00255.html>
--
Yao (齐尧)
next prev parent reply other threads:[~2014-09-15 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 19:45 David Taylor
2014-09-15 4:04 ` Yao Qi [this message]
2014-09-15 14:19 ` David Taylor
2014-09-18 13:38 ` Yao Qi
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=87iokp4joy.fsf@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dtaylor@emc.com \
--cc=gdb@sourceware.org \
/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