Hi Denis,

this is fixed in VMMaker.oscog-eem.2032. I'll generate sources and push to github presently. Thanks for the test case. This is a "new" case the VM has to deal with with the "new" callPrimitive byte code. I had written the code to handle the case quite a while ago (2013?) but had written incorrect code.

On Thu, Dec 8, 2016 at 9:31 AM, Eliot Miranda <eliot.miranda@gmail.com> wrote:

Hi Denis,

On Mon, Dec 5, 2016 at 6:29 AM, Denis Kudriashov <dionisiydk@gmail.com> wrote:

2016-12-05 15:25 GMT+01:00 Denis Kudriashov <dionisiydk@gmail.com>:
I found automated way how to check problem:

p := [ Object basicSize ] fork.
p suspend.

3 timesRepeat: [p step: p suspendedContext].
newContext := p completeStep: p suspendedContext.
newContext selector. "=> doesNotUnderstand:"
newContext arguments first selector == 0

Thanks. This reproduces in the simulator. The interpreter is accessing byte codes beyond the return at the end of Object>>#basicSize. I should be bale to understand this better soon.

And arguments of DNU message argument is also very strange:
newContext arguments first arguments "an Array(0 Context>>jump)"

--
_,,,^..^,,,_
best, Eliot

_,,,^..^,,,_

best, Eliot