Mmmm guessing shows that ensuring forceInterruptCheck is called after dispatchFunctionPointer DOESN'T make the profile correct. So I'll wait for the true answer...
On 28-Feb-09, at 4:35 PM, John M McIntosh wrote:
Oops you CANN'T just call checkForInterrupts from dispatchFunctionPointer that makes squirrel food of object memory later in time (no idea why).
The safe way is to get the before and after time, then if they are different then call forceInterruptCheck
-- = = = ======================================================================== John M. McIntosh johnmci@smalltalkconsulting.com Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================