From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10943] New: Support generic @entry saving in .return probes
Date: Thu, 12 Nov 2009 00:58:00 -0000 [thread overview]
Message-ID: <20091112005815.10943.jistone@redhat.com> (raw)
We already support implicitly saving $target variables at function entry for use
in a .return probe (though bug #5899 debates when ->members should be read).
There's a good idea in bug #5899 comment #4 to support saving arbitrary
expressions as well. I quite like the example:
probe FOO.return {
println(gettimeofday_ns() - @entry(gettimeofday_ns()))
}
This @entry syntax is somewhat distinct from #5899, so I thought it should be
its own bug.
I think our traditional saved_var[tid()] mechanism could be adapted for this
pretty easily. The newer method using the kretprobe data pouch (bug #5916) is a
little tricker though, as it would need the types to be resolved a bit earlier
than we do now.
--
Summary: Support generic @entry saving in .return probes
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jistone at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10943
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-11-12 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 0:58 jistone at redhat dot com [this message]
2009-11-12 0:59 ` [Bug translator/10943] " jistone at redhat dot com
2009-11-12 1:27 ` jistone at redhat dot com
2010-01-18 20:17 ` fche at redhat dot com
2010-06-24 14:23 ` jistone at redhat dot com
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=20091112005815.10943.jistone@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).