public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Kevin Jia <jiaminghao@gmail.com>,
	SystemTAP <systemtap@sources.redhat.com>
Subject: Re: help-inode-watch error
Date: Fri, 31 Mar 2006 03:45:00 -0000	[thread overview]
Message-ID: <442CA5F0.4070500@redhat.com> (raw)
In-Reply-To: <30c154100603301724u4a967b8bgab10156c5d4befca@mail.gmail.com>

Kevin Jia wrote:
>>Which version of systemtap are you using? It looks like the version of
>>stap you are using is interpretting them as local variables. Do you have
>>a relatively recent version of stap (one around mid march))?
> 
> 
> Version of systemtap is  0.5.3 build 01-17-2006. Can you send me the
> new version ?

There are instructions on build the latest version at:

http://sourceware.org/systemtap/build.html

> I am a beginner of systemtap. I have think
> about this carefully, but also have many confusions that how use
> systemtap trace interrupt. Does systemtap can recognise the function
> "foo_interrupt_handler", "bar_interrupt_handler"...? Can you support
> me a example about trace a interrupt? I need the detail to research
> vexedly.
> 
> thank you very much.

I am not quite sure what your question is. SystemTap can place probes on 
various functions in the kernel. If the naming scheme of the interrupts 
is reasonable, you could use the wild card notation to put probes on a 
group of functions. You might do a "man stapprobes" to get more 
information about that.

cscope can give you some insight in the the static call tree in the kernel.

http://cscope.sourceforge.net/

-Will

      parent reply	other threads:[~2006-03-31  3:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 11:31 Kevin Jia
2006-03-30 14:48 ` William Cohen
     [not found]   ` <30c154100603301724u4a967b8bgab10156c5d4befca@mail.gmail.com>
2006-03-31  3:45     ` William Cohen [this message]

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=442CA5F0.4070500@redhat.com \
    --to=wcohen@redhat.com \
    --cc=jiaminghao@gmail.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).