Re: DTrace probe problem
Re: DTrace probe problem
- Subject: Re: DTrace probe problem
- From: radj <email@hidden>
- Date: Tue, 27 May 2008 14:26:39 +0800
>
> dtrace allows you to specify the command to be run on the command line.
> See this post:
>
>
> http://www.friday.com/bbum/2008/01/26/objective-c-printing-class-name-from-dtrace/
>
>
Clearly, I still have alot to learn about DTrace.
> Specifically, you can do something like this:
>
> sudo dtrace -s forwardMethod.d -c
> /Applications/TextEdit.app/Contents/MacOS/TextEdit
> This, of course, ends up running said application as root, which may not be
> acceptable in your case.
>
Unfortunately, it isn't since I'm working on a driver and the OS is the one
who invokes it. Also, the OS provides lots of arguments to the app, it would
be hard to mimic from command line.
>
> An alternative solution would be to make your application wait until you
> have "connected" dtrace to it and then pass a signal -- could be a literal
> signal -- to continue execution.
I would like to learn how to do this, do you have any posts on your blog
about this? It would be really helpful.
Our aim is to remove the need to make a Debug build to debug the driver and
using DTrace seems to be alternative to make the least adjustments within
code. I hope future replies won't question the approach but rather talk
about how to work the DTrace. :)
>
> b.bum
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden