Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: [doc/tracepoint] Add a note for assigning values of inferior to trace state variables
Date: Fri, 16 Sep 2011 09:07:00 -0000	[thread overview]
Message-ID: <CANFwon3WmN=06vh-bYi66XTMOX8KgTGk6udSNWWdyKU0e4_7OQ@mail.gmail.com> (raw)

Hi,

I talk about a bug about assigning values of inferior to trace state variables
http://sources.redhat.com/ml/gdb/2011-07/msg00009.html

this issue can be handle by convert value to (uint64_t), for example:
teval $tmp=(uint64_t)a

So I make a patch to update the doc.

Please help me review it.

Thanks,
Hui

2011-09-16  Hui Zhu  <teawater@gmail.com>

	* gdb.texinfo (Tracepoint Action Lists): Add a note for assigning
	values of inferior to trace state variables.

---
 doc/gdb.texinfo |    6 ++++++
 1 file changed, 6 insertions(+)

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -10321,6 +10321,12 @@ are discarded, so this is mainly useful
 state variables (@pxref{Trace State Variables}) without adding those
 values to the trace buffer, as would be the case if the @code{collect}
 action were used.
+Please note that if you want assigning values of inferior to trace state
+variables, please convert it to unsigned 64bit first.  For example:
+
+@smallexample
+>teval $c=(uint64_t)jiffies_64
+@end smallexample

 @kindex while-stepping @r{(tracepoints)}
 @item while-stepping @var{n}


             reply	other threads:[~2011-09-16  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16  9:07 Hui Zhu [this message]
2011-09-16  9:48 ` Eli Zaretskii
2011-09-16 20:37   ` Joel Brobecker
2011-09-17 14:40     ` Hui Zhu
2011-09-21 17:01       ` Pedro Alves
2011-09-16 12:26 ` Pedro Alves

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='CANFwon3WmN=06vh-bYi66XTMOX8KgTGk6udSNWWdyKU0e4_7OQ@mail.gmail.com' \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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