[Vm-dev] [error] running script BuildSqueakSpurTrunkVMMakerImage.st

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Mon Mar 2 09:48:58 UTC 2020


But FFICallbackThunk initialize requires Alien initialize...
I think that I've just fixed it (to be tested).

But then, I get another error when evaluating:
Spur32to64BitBootstrap new bootstrapImage: 'trunk50'.

I see no such class.
Eliot, could you point us to the appropriate MC package?

Le lun. 2 mars 2020 à 10:21, Nicolas Cellier <
nicolas.cellier.aka.nice at gmail.com> a écrit :

> Hi Robert,
> confirmed, thanks for reporting.
> It seems that there is a problem with Monticello initialization order.
>
> One should invoke "FFICallbackThunk initialize" before "Callback
> initialize" because the later wants to be added in startup list after the
> former...
> Unfortunately, MC initialization order seems to be random...
> We should find a workaround...
>
> In the interim, you could try to evaluate
> FFICallbackThunk initialize
> then restart Callback class>>initialize from the debugger...
>
> Le lun. 2 mars 2020 à 06:52, Robert <robert.withers at pm.me> a écrit :
>
>>
>> As soon as Spur64VMMaker.image is made from trunk6-64.image and starts
>> the error occur immediately with a dialog which states 'Initializing
>> Alien-Core-TorstenBergman.101'
>>
>> On 3/2/20 12:37 AM, Robert wrote:
>> > In building the spurtrunkvmmaker64 image, at some point, after loading
>> > Alien, the script BuildSqueakSpurTrunkVMMakerImage.st throws an
>> error...
>> >
>> > 'FFICallbackThunk cannot be found in the list.'
>> >
>> > --- The full stack ---
>> > SmalltalkImage(Object)>>error:
>> > SmalltalkImage>>add:toList:after:
>> > SmalltalkImage>>addToStartUpList:after:
>> > Callback class>>ensureNotifiedAtStartup
>> > Callback class>>initialize
>> > MCMethodDefinition>>postload
>> > MCMethodDefinition(MCDefinition)>>postloadOver:
>> >
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20200302/9434c25e/attachment.html>


More information about the Vm-dev mailing list