From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/14924] warn on complex $ptr->foo expressions in .return probes
Date: Tue, 08 Nov 2016 18:54:00 -0000 [thread overview]
Message-ID: <bug-14924-6586-NIOMqMaT5E@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14924-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14924
--- Comment #5 from Josh Stone <jistone at redhat dot com> ---
If you're going to make a broad warning, please do switch the tapsets to share
in the users' pain. (i.e. don't suppress the warning -- dogfood it)
But again, remember PR18579 that autocast @entry($foo)->bar doesn't work,
whereas it does work with implicit entry-value saving. Maybe this can be
partially kludged by special-casing @entry on a plain target value.
IIRC, @entry doesn't use kretprobe pouches either, for the similar reason that
the expression type may not be fully known yet.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-11-08 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 21:49 [Bug translator/14924] New: " fche at redhat dot com
2016-10-17 15:31 ` [Bug translator/14924] " mcermak at redhat dot com
2016-10-17 17:24 ` jistone at redhat dot com
2016-11-08 9:36 ` mcermak at redhat dot com
2016-11-08 18:39 ` fche at redhat dot com
2016-11-08 18:54 ` jistone at redhat dot com [this message]
2016-11-10 15:32 ` mcermak at redhat dot com
2016-11-10 19:16 ` fche at redhat dot com
2016-11-11 12:17 ` mcermak at redhat dot com
2016-11-11 17:00 ` jistone at redhat dot com
2016-11-14 15:51 ` mcermak at redhat dot com
2016-11-18 13:32 ` mcermak at redhat dot com
2016-11-18 15:25 ` mcermak 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-14924-6586-NIOMqMaT5E@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).