Re: Thread ID in crash log

that will match with crash log's thread numbers? :D ex: fwrite(filePointer, [thread:%d] a trivial sample debug log line showing the thread number\n, ); // what should go in the blank? Cheers, radj ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com

Re: Thread ID in crash log

(...) because there are alot all over the code (not the best practice, me thinks). But thanks to your intro to task_threads(), I can follow the idea and try my own array of threads. This gives me something to start on! Appreciate it. =) - radj ___ Cocoa

Re: Thread ID in crash log

I've done it that way when debugging threads. It doesn't take long; none of the calls take very long, But there's still a difference, right? And when called or passed through alot, that small difference can become really big. especially when compared to what goes on when writing to a log

Thread ID in crash log

Hello List, I've been googling and searching for this but to no joy. How do you get a thread ID of the current thread that will be similar with the one that shows up on a crash log? This is pretty helpful for debugging multi-threaded applications. Thanks, Radj

Re: DTrace probe problem

previliges than _lp user can give. And I've read that authentication is a little complicated. I bet I can find lots of examples of running stuff as root in other threads. Thanks for all your help, guys! radj ___ Cocoa-dev mailing list (Cocoa-dev

Re: DTrace probe problem

in the error? Cheers, radj ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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

Re: DTrace probe problem

I tried the raise() in D script. My driver got the signal but it kinda malfunctioned, it got stuck somehow although it still can accept any signal. Weird. My small experience can't tell me anything. So I googled up some more D trace commands and found system(). I tried this instead:

Re: DTrace probe problem

finished compiling and not when a probe fires? Curious, radj ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help

Solved (still open to suggestions): DTrace probe problem

Finally got it to poll. I had to study signals and signal handling within the driver. lol. I've tried it and atleast it helps me delay the actual initialization of the driver while I run the D script. Your quick responses were really helpful. Thanks alot, Bill! DTrace rocks! radj On Mon, Jun 2

Re: DTrace probe problem

Personally, I would start by trying to use a signal handler. See x-man-page://signal (the signal man page). Specifically, I would write a handler for SIGUSR1 or SIGUSR2 as those exist explicitly to offer user specific behaviors. Take a command line option or read an environment variable