which function is instrumentable?

Adrien Kunysz adrien@kunysz.be
Wed Mar 23 07:49:00 GMT 2011


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".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://sourceware.org/pipermail/systemtap/attachments/20110323/12d2aea9/attachment.sig>


More information about the Systemtap mailing list