• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Solved (still open to suggestions): DTrace probe problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Solved (still open to suggestions): DTrace probe problem


  • Subject: Solved (still open to suggestions): DTrace probe problem
  • From: radj <email@hidden>
  • Date: Tue, 3 Jun 2008 12:45:01 +0800

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, 2008 at 10:31 AM, Bill Bumgarner <email@hidden> wrote:

> On Jun 1, 2008, at 7:19 PM, radj wrote:
>
>> I can try that. Sounds like a good idea. Make the "waiting for the signal"
>> the first thing the driver will do. but how do you send a signal from within
>> DTrace to a specific process?
>>
>
> I have no idea if dtrace can send a signal.   I would send a kill -USR1 via
> a shell command...
>
> 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

  • Prev by Date: Re: Key-Value pairs
  • Next by Date: Re: Main window disappears. Sometimes.
  • Previous by thread: Re: Hillegass book memory question
  • Next by thread: CoreData file format stability
  • Index(es):
    • Date
    • Thread