From: "guanglei at cn dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/2433] sys_groupexit in blacklist
Date: Thu, 06 Apr 2006 03:43:00 -0000 [thread overview]
Message-ID: <20060406034317.21974.qmail@sourceware.org> (raw)
In-Reply-To: <20060308075244.2433.guanglei@cn.ibm.com>
------- 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.
next prev parent reply other threads:[~2006-04-06 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 7:52 [Bug tapsets/2433] New: " guanglei at cn dot ibm dot com
2006-04-06 3:02 ` [Bug tapsets/2433] " guanglei at cn dot ibm dot com
2006-04-06 3:17 ` fche at redhat dot com
2006-04-06 3:43 ` guanglei at cn dot ibm dot com [this message]
2006-05-05 18:02 ` eteo at redhat dot com
2006-06-02 18:34 ` 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=20060406034317.21974.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).