From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2152] New: jprobe variant to run handler instead of probed function
Date: Fri, 13 Jan 2006 23:26:00 -0000 [thread overview]
Message-ID: <20060113232600.2152.jkenisto@us.ibm.com> (raw)
A kprobes user has asked for the ability to use kprobes to turn a specified
function into a no-op. I couldn't figure out how to do that (Any ideas?), but
it occurred to us that jprobes takes us partway there.
Our user's request could be viewed as a special case of a more general feature:
the ability to execute a jprobe-like handler instead of (rather than before)
executing the probed function.
--
Summary: jprobe variant to run handler instead of probed function
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P3
Component: kprobes
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jkenisto at us dot ibm dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=2152
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2006-01-13 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 23:26 jkenisto at us dot ibm dot com [this message]
2006-01-16 10:56 ` Suparna Bhattacharya
2006-01-16 10:56 ` [Bug kprobes/2152] " suparna at in dot ibm dot com
2006-01-16 17:26 ` anil dot s dot keshavamurthy at intel dot com
2006-01-17 6:04 ` Suparna Bhattacharya
2006-01-17 6:04 ` suparna at in dot ibm dot com
2007-02-17 11:35 ` srinivasa at in dot ibm dot com
2007-02-17 11:40 ` srinivasa at in dot ibm dot com
2007-08-19 5:18 ` jkenisto at us dot ibm dot com
2009-01-06 18:43 ` jkenisto at us dot ibm 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=20060113232600.2152.jkenisto@us.ibm.com \
--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).