This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: which function is instrumentable?

From: Adrien Kunysz <adrien at kunysz dot be>
To: Zhiwei Ying <zhiwei dot ying at gmail dot com>
Cc: systemtap <systemtap at sources dot redhat dot com>
Date: Wed, 23 Mar 2011 07:49:18 +0000
Subject: Re: which function is instrumentable?
References: <AANLkTi=dQW+9cDd_NtmKygbdY9O8qK49=fLePCki1q-M@mail.gmail.com>

On Wed, Mar 23, 2011 at 09:22:12AM +0800, Zhiwei Ying wrote:
> I tried to trace down every function in a device driver, but it fails.
> It may be cased too many instrumentation. But the problem is how can I
> know which function is instrumentable and which is not? Or I have to
> manually narrow the problem? Any idea?

This

	$ stap -l 'module("foo").function("*")'

is supposed to give you a list of all the "probeable" functions in
module "foo".

Attachment: signature.asc
Description: Digital signature

Follow-Ups:
- Re: which function is instrumentable?
  - From: Zhiwei Ying

References:
- which function is instrumentable?
  - From: Zhiwei Ying

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]