From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12706 invoked by alias); 12 Nov 2009 00:58:27 -0000 Received: (qmail 12678 invoked by uid 48); 12 Nov 2009 00:58:15 -0000 Date: Thu, 12 Nov 2009 00:58:00 -0000 From: "jistone at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20091112005815.10943.jistone@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/10943] New: Support generic @entry saving in .return probes X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00495.txt.bz2 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.