On 24 May 2010 01:40, Bert Freudenberg <bert at freudenbergs.de> wrote:
> On 23.05.2010, at 23:24, Eliot Miranda wrote:
>> Hi Michael, Michael, Dennis, Hi All,
>>
>>     I think this is a simple bug in ContextPart >> #tryNamedPrimitiveIn:for:withArgs:, which neglects to flush the method cache for the method and/or selector used to simulate execution of a named primitive.  With the relevant flushCacher calls added I no longer see any of the simulation failures recently experienced (someMethod getSourceFromFile, TimeStamp now).  Please test the attached and let me know how you get on.
>>
>> The problem is caused by using the same method to invoke differet primitives in quick succession where, because the method cache is not flushed, the wrong primitive (a previous primitive) is left in the cache and invoked instead of the desired primitive.
>
> That's been bugging me for some time. Yay!
>
mee tooo :)
Btw, i had to patch exactly this method in order to be able to handle
step over the native code primitive
to avoid entering the smalltalk code if prim fails.

> - Bert -
>
>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.