Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More IOTimerEventSource behavior

Many thanks to gvdl for the info regarding calling conventions. At this point the question has shifted to "How is it that a different value comes in as 'sender' every time the IOTimerEventSource fires?

For example - on three occasions a timer was set and then the timeout occurred:

workloop*           = 0x02D438C0
IOTimerEventSource* = 0x30D082D0

1) timeoutOccurred: sender = 0x036D6740, this = 0x02E94000, theOwner = 0
2) timeoutOccurred: sender = 0x03697980, this = 0x02E94000, theOwner = 0
3) timeoutOccurred: sender = 0x03695A40, this = 0x02E94000, theOwner = 0

The WorkLoop was not changed, the same IOTimerEventSource was in play, the only thing that happened was to call "mTimerSource->setTimeoutMS(kTIMEOUT);"

So how is it that the 'sender' keeps coming back as a different value?

Thanks!

Lance Drake

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-drivers/email@hidden

This email sent to email@hidden
References: 
 >IOTimerEventSource behavior (From: Lance Drake <email@hidden>)
 >Re: IOTimerEventSource behavior (From: Godfrey van der Linden <email@hidden>)
 >Re: IOTimerEventSource behavior (From: Godfrey van der Linden <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.