public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: systemtap@sources.redhat.com
Subject: Plain kprobe genearation/bisect script
Date: Tue, 07 Apr 2009 08:59:00 -0000	[thread overview]
Message-ID: <49DB15D4.1070508@linux.vnet.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

Hi All,

I have implemented shell scripts that helps me to narrow down a faulty 
probe that causes problem/crash, while debugging systemtap issues. As 
per the discussion in weekly systemtap meeting dated 12th March 2009, I 
am attaching these scripts (kp_bisect.tgz) that may help us in 
identifying probes that can be a potential candidate for blacklist. 
These scripts will help user to extract probes (probe function name) 
from stap generated C module and test plain kprobes/kretprobes allowing 
user to run bisect-like functionality to narrow down to a single faulty 
probe. It does handle ".call" and ".return" probes.

Can someone can take look at these scripts and see if these can be used 
as a base for automating the process of testing kprobes for black/white 
list generation? The file "README.txt" describes the steps to use these 
scripts.

Thanks,
-Mahesh.

[-- Attachment #2: kp_bisect.tgz --]
[-- Type: application/x-compressed-tar, Size: 20397 bytes --]

             reply	other threads:[~2009-04-07  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  8:59 Mahesh Jagannath Salgaonkar [this message]
2009-04-09 15:16 ` Plain kprobe genearation/bisect script - latest changes Mahesh Jagannath Salgaonkar
2009-05-05 15:58   ` David Smith

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=49DB15D4.1070508@linux.vnet.ibm.com \
    --to=mahesh@linux.vnet.ibm.com \
    --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).