This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/2433] sys_groupexit in blacklist
- From: "guanglei at cn dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 6 Apr 2006 03:43:17 -0000
- Subject: [Bug tapsets/2433] sys_groupexit in blacklist
- References: <20060308075244.2433.guanglei@cn.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From guanglei at cn dot ibm dot com 2006-04-06 03:43 -------
(In reply to comment #2)
> It must indeed be just a typo.
>
> However, I wonder whether the kretprobes situation is such that these two
> blacklist items are no longer needed. Or for that matter, why does
> src/tapset/syscalls.stp make ".return" probe aliases to either of these two
> never-returning calls.
I think the syscall.exit & syscall.exit_group should be deleted from
src/tapset/syscalls.stp. And do_exit should also be added into blacklist.
For these never-return functions, it won't cause runtime error if a return probe
is putting on them since these probes will never be hit. But making tapsets.cxx
give warnings about return probles on these never-return functions could let the
user know it's useless to do that, instead of waiting for executions of probe
handlers. Not all users know about these never-return functions.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2433
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.