This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/11553] need better message for return probe on inline function
- From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 28 Apr 2010 18:34:46 -0000
- Subject: [Bug translator/11553] need better message for return probe on inline function
- References: <20100428174306.11553.jkenisto@us.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jkenisto at us dot ibm dot com 2010-04-28 18:34 -------
(In reply to comment #1)
> This is very similar to bug #5076.
As I should have mentioned, I looked at both #4413 and #5076 before I filed
this. This is related, but a different issue.
> It gets even harder when there's a wildcard
> in the function name -- if every match happens to be an inline, how should we
> warn about this?
The message you currently give is the same no matter whether it's an
un-wildcarded name with no match (i.e., no return probe possible) or a
wildcarded name with 0 matches, right? It'd be nice if you could notice that
multiple functions were found but couldn't be probed, and change the message to:
(These functions are inlined, so no return probes are possible.)
The question you didn't ask -- What, if anything, do we say if some matched
functions are inline and some aren't? -- is an interesting one, but the scope of
that issue is larger than the one this PR is concerned with. stap -l is
presumably enlightening in those situations.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11553
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.