From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/5899] $ptr->member in return probe
Date: Thu, 12 Nov 2009 01:27:00 -0000 [thread overview]
Message-ID: <20091112012709.10768.qmail@sourceware.org> (raw)
In-Reply-To: <20080308010658.5899.jkenisto@us.ibm.com>
------- Additional Comments From jistone at redhat dot com 2009-11-12 01:27 -------
(In reply to comment #4)
> probe FOO.return {
> println(@cast(@entry($param),"struct foo")->field))
> }
If we decide to make $param->field implicitly work this way, then we can use the
same internal mechanisms as @cast without requiring the user to know the type.
We can translate the pointer alone, and then pass that type die to
dwflpp::literal_stmt_for_pointer to read the rest, so we get two generated
functions:
$param->field ==> _dwarf_tvar_get_cast_1(@entry(_dwarf_tvar_get_param_0()))
The @entry processing can go from here to save the expression as needed.
--
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |10943
http://sourceware.org/bugzilla/show_bug.cgi?id=5899
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2009-11-12 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 1:07 [Bug translator/5899] New: " jkenisto at us dot ibm dot com
2008-03-10 22:05 ` [Bug translator/5899] " mhiramat at redhat dot com
2008-03-11 20:20 ` jkenisto at us dot ibm dot com
2008-03-11 22:00 ` mhiramat at redhat dot com
2008-06-06 14:09 ` mark at klomp dot org
2009-01-23 18:10 ` fche at redhat dot com
2009-01-27 16:50 ` ananth at in dot ibm dot com
2009-01-28 2:39 ` jkenisto at us dot ibm dot com
2009-10-23 23:20 ` roland at gnu dot org
2009-11-12 1:27 ` jistone at redhat dot com [this message]
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=20091112012709.10768.qmail@sourceware.org \
--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).