dtrace discuss - Nov 2006 - problem with dtrace toolkit

I tried some of the scripts in the toolkit  (opensnoop, execsnoop, dtruss), and
I keep seeing errors like this:

dtrace: error on enabled probe ID 3 (ID 113: syscall::exece:return): invalid
kernel access in action #5 at DIF offset 0

Anyone know what could be the problem?

TIA
 
 
This message posted from opensolaris.org

G''Day Kelvin,

On Wed, Nov 15, 2006 at 02:31:46PM -0800, kelvin wrote:
> I tried some of the scripts in the toolkit  (opensnoop, execsnoop, dtruss),
and I keep seeing errors like this:
> 
> dtrace: error on enabled probe ID 3 (ID 113: syscall::exece:return):
invalid kernel access in action #5 at DIF offset 0
> 
> Anyone know what could be the problem?
These scripts shouldn''t have a problem; to eliminate factors, can you
try
as root in the global zone? - that is, if you wern''t doing this
already. :)

also trying the oneliners in Docs/oneliners.txt will help - if any of
them error, it gives us fewer factors to troubleshoot.

cheers,

Brendan

Hi Brendan

Hmm... I think this might be an access issue. I tried the oneliners and the only
onces that seem to work are the syscall ones. I did a ''dtrace
-l'' and it looks like the list only has syscall and profile providers.

I have also been having trouble with very basic pid provider scripts.

For example, I tried a simple script like this:

pid$1:::entry
{
        self->trace = 1;
}

The pid I run it with clearly exists, but dtrace just says probe description
does not match any probes.

I''ll get the Unix admin to give me more rights.

Thanks Brendan.
 
 
This message posted from opensolaris.org