Re: DTrace Questions
Re: DTrace Questions
- Subject: Re: DTrace Questions
- From: Eric Gorr <email@hidden>
- Date: Thu, 6 May 2010 20:24:50 -0400
When I try this, I am getting an error:
> sudo dtrace -n 'pid140:myApp::entry { printf( "%s", execname ) }'
dtrace: invalid probe specifier pid140:myApp::entry { printf( "%s", execname ) }: failed to create entry probe for '-[NNASoundManager initializeSounds]': Invalid argument
Is it really necessary to place myApp in the dtrace command?
From my limited understanding, it seems like this:
> sudo dtrace -n 'pid140:::entry { printf( "%s", execname ) }'
should be sufficient as there won't be anything else with the same process id.
On May 6, 2010, at 5:50 PM, Franklin Marmon wrote:
>
> This may not be what you are looking for, but it prints entry points for all my application's functions.
>
> sudo dtrace -n 'pid[MYPID]:[APPNAME]::entry { printf( "%s", execname ) }'
>
> replacing [MYPID] and [APPNAME] as appropriate for your target application. Obviously the same thing is possible for return functions too.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden