dtrace discuss - Apr 2007 - Limiting trace information in pid provider

This is probably simple but being a noob I don''t see how to handle it
--- I''d like to use a conventional pid provider to capture
entry/return as with userfunc.d, BUT I''d like to filter out events in
libc and/or system calls.  The idea is to be able to see what IK''m
doing, but not so much what the sun libraries are doing.

Thanks for ideas

Charlie

-- 
Laissez-nous faire, laissez-nous passer.
Le monde va de lui-m?me.

Hi Charlie,

You can specify the modules you''d like to trace in the probe
description

pid$target:<mylibrary>.so.1::entry

pid$target:<mylib1>.so.1::entry,
pid$target:<mylib2>.so.1::entry

or you could use a predicate to filter out libc calls (though you''ll
still
induce the overhead of the instrumentation):

pid$target:::entry
/probemod != "libc.so.1"/

Unless you''re using the syscall provider, you won''t see actual
system calls --
just their libc wrappers.

Adam

On Wed, Apr 18, 2007 at 03:08:55PM -0600, Charles Martin
wrote:
> This is probably simple but being a noob I don''t see how to handle
it
> --- I''d like to use a conventional pid provider to capture
> entry/return as with userfunc.d, BUT I''d like to filter out events
in
> libc and/or system calls.  The idea is to be able to see what IK''m
> doing, but not so much what the sun libraries are doing.
> 
> Thanks for ideas
> 
> Charlie
> 
> -- 
> Laissez-nous faire, laissez-nous passer.
> Le monde va de lui-m?me.
> _______________________________________________
> dtrace-discuss mailing list
> dtrace-discuss at opensolaris.org
-- 
Adam Leventhal, Solaris Kernel Development       http://blogs.sun.com/ahl