From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/14079] New: caller() pass-4 error if no uretprobes in script
Date: Tue, 08 May 2012 16:16:00 -0000 [thread overview]
Message-ID: <bug-14079-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14079
Bug #: 14079
Summary: caller() pass-4 error if no uretprobes in script
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: fche@redhat.com
Classification: Unclassified
stap -e 'probe module("tun").function("tun_net_xmit@drivers/net/tun.c").call {
printf("tun_net_xmit %x from %s\n", $skb->ip_summed, caller()); }'
results in a stap -p4 compilation error, due to this bit in the caller
embedded-c:
#ifdef STAPCONF_UPROBE_GET_PC
else if (CONTEXT->probe_type == _STP_PROBE_HANDLER_URETPROBE)
THIS->__retvalue =
(int64_t)(long)_stp_ret_addr_r(CONTEXT->ips.ri);
#endif
with apparently no one including enough uprobes.h goop to make this from
runtime/common_probe_context.h compilable:
/* uretprobe state */
struct uretprobe_instance *ri;
This could be fixed a couple of ways, but my favorite would be to use this as
an opportunity to do bug #6580, which would reimplement caller() etc. in terms
of backtracing functions instead of such low-level embedded-c runes.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-05-08 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 16:16 fche at redhat dot com [this message]
2012-05-08 16:20 ` [Bug tapsets/14079] " fche 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=bug-14079-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).