OpenSmalltalk
primitiveNewCPU failed when trying to start CogVMSimulator
I am trying to set up a working VMMaker image for the first time. I have strictly followed the instructions from https://wiki.squeak.org/squeak/vmmaker. After opening the SpurVMMaker64.image image, I ran ./buildspurtrunkreader64image.sh and tried the first do-it from the VM Simulation Workspace. Independently of which infrastructure I choose from the pop-up (ARMv8 or X64), I immediately see an Error: primitiveNewCPU failed from GdbARMv8Alien64 or BochsX64Alien64, resp. I have also tried most other do-its from the simulation workspace, but they all fail with the same error. However, some fail with a MessageNotUnderstood: UndefinedObject>>- from StackInterpreterSimulatorLSB(StackInterpreter)>>mapTraceLog instead because traceLogIndex is nil.
What am I missing? Am I expected to build a VM first to run the VMMaker image in it ?(I am also facing several problems when trying to build the VM.)
Hi Christoph, the documentation could be better. The simulator will work with the StackInterpreter without additional support.To run the CoInterpreter one needs one or more processor simulator plugins. These are not included with standard VMs. The plugins are only built in one’s own VM builds if the support libraries are built. See the bochsx86, bochsx64, gdbarm32, and gdbarm64 directories at the top levels of building subdirectories, e.g. building/linux64x64/{bochsx86,bochsx64,gdbarm32,gdbarm64}. These have makeem scripts in them. Only the macos64 scripts are used with any regularity.So to simulate a Cog VM- build the support libraries for the processors you want to use for your platform- make a squeak.cog.spur VM For your platform- use this VM to build/run your VMMaker imageThe standard VMs ,,,^..^,,, (phone)On Apr 7, 2025, at 1:40 PM, Christoph Thiede @.> wrote: I am trying to set up a working VMMaker image for the first time. I have strictly followed the instructions from https://wiki.squeak.org/squeak/vmmaker. After opening the SpurVMMaker64.image image, I ran ./buildspurtrunkreader64image.sh and tried the first do-it from the VM Simulation Workspace. Independently of which infrastructure I choose from the pop-up (ARMv8 or X64), I immediately see an Error: primitiveNewCPU failed from GdbARMv8Alien64 or BochsX64Alien64, resp. I have also tried most other do-its from the simulation workspace, but they all fail with the same error. However, some fail with a MessageNotUnderstood: UndefinedObject>>- from StackInterpreterSimulatorLSB(StackInterpreter)>>mapTraceLog instead because traceLogIndex is nil. What am I missing? Am I expected to build a VM first to run the VMMaker image in it?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.>
LinqLover created an issue (OpenSmalltalk/opensmalltalk-vm#711) I am trying to set up a working VMMaker image for the first time. I have strictly followed the instructions from https://wiki.squeak.org/squeak/vmmaker. After opening the SpurVMMaker64.image image, I ran ./buildspurtrunkreader64image.sh and tried the first do-it from the VM Simulation Workspace. Independently of which infrastructure I choose from the pop-up (ARMv8 or X64), I immediately see an Error: primitiveNewCPU failed from GdbARMv8Alien64 or BochsX64Alien64, resp. I have also tried most other do-its from the simulation workspace, but they all fail with the same error. However, some fail with a MessageNotUnderstood: UndefinedObject>>- from StackInterpreterSimulatorLSB(StackInterpreter)>>mapTraceLog instead because traceLogIndex is nil. What am I missing? Am I expected to build a VM first to run the VMMaker image in it?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
On Apr 7, 2025, at 1:40 PM, Christoph Thiede @.> wrote: I am trying to set up a working VMMaker image for the first time. I have strictly followed the instructions from https://wiki.squeak.org/squeak/vmmaker. After opening the SpurVMMaker64.image image, I ran ./buildspurtrunkreader64image.sh and tried the first do-it from the VM Simulation Workspace. Independently of which infrastructure I choose from the pop-up (ARMv8 or X64), I immediately see an Error: primitiveNewCPU failed from GdbARMv8Alien64 or BochsX64Alien64, resp. I have also tried most other do-its from the simulation workspace, but they all fail with the same error. However, some fail with a MessageNotUnderstood: UndefinedObject>>- from StackInterpreterSimulatorLSB(StackInterpreter)>>mapTraceLog instead because traceLogIndex is nil. What am I missing? Am I expected to build a VM first to run the VMMaker image in it?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.>
LinqLover created an issue (OpenSmalltalk/opensmalltalk-vm#711) [snip], resp. I have also tried most other do-its from the simulation workspace, but they all fail with the same error. However, some fail with a MessageNotUnderstood: UndefinedObject>>- from StackInterpreterSimulatorLSB(StackInterpreter)>>mapTraceLog instead because traceLogIndex is nil.This regression is fixed in VMMaker.oscog-eem.3542. Apologies. What am I missing? Am I expected to build a VM first to run the VMMaker image in it?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Hi Christoph, the documentation could be better. The simulator will work with the StackInterpreter without additional support.To run the CoInterpreter one needs one or more processor simulator plugins. These are not included with standard VMs. The plugins are only built in one’s own VM builds if the support libraries are built. See the bochsx86, bochsx64, gdbarm32, and gdbarm64 directories at the top levels of building subdirectories, e.g. building/linux64x64/{bochsx86,bochsx64,gdbarm32,gdbarm64}. These have makeem scripts in them. Only the macos64 scripts are used with any regularity.So to simulate a Cog VM- build the support libraries for the processors you want to use for your platform- make a squeak.cog.spur VM For your platform- use this VM to build/run your VMMaker imageThe standard VMs
Thank you for the explanation! We now got it working and I was able to run a BouncingAtomsMorph in the simulator morph. :-)
Improving the docs could indeed be helpful for newbies such as us. Maybe we can add some more explicit pointers on this soon. I'm leaving it up to you to keep this issue open until this has been achieved :)
On Wed, Apr 9, 2025 at 11:48 AM Christoph Thiede @.***> wrote:
Hi Christoph, the documentation could be better. The simulator will work with the StackInterpreter without additional support.To run the CoInterpreter one needs one or more processor simulator plugins. These are not included with standard VMs. The plugins are only built in one’s own VM builds if the support libraries are built. See the bochsx86, bochsx64, gdbarm32, and gdbarm64 directories at the top levels of building subdirectories, e.g. building/linux64x64/{bochsx86,bochsx64,gdbarm32,gdbarm64}. These have makeem scripts in them. Only the macos64 scripts are used with any regularity.So to simulate a Cog VM- build the support libraries for the processors you want to use for your platform- make a squeak.cog.spur VM For your platform- use this VM to build/run your VMMaker imageThe standard VMs
Thank you for the explanation! We now got it working and I was able to run a BouncingAtomsMorph in the simulator morph. :-)
Improving the docs could indeed be helpful for newbies such as us. Maybe we can add some more explicit pointers on this soon. I'm leaving it up to you to keep this issue open until this has been achieved :)
— Reply to this email directly, view it on GitHub https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/711#issuecomment-2790641689, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADY5VUDDXMUFMOQIZLMGAQL2YVTRRAVCNFSM6AAAAAB2UR2CF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJQGY2DCNRYHE . You are receiving this because you commented.Message ID: @.***> LinqLover left a comment (OpenSmalltalk/opensmalltalk-vm#711) https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/711#issuecomment-2790641689
Hi Christoph, the documentation could be better. The simulator will work with the StackInterpreter without additional support.To run the CoInterpreter one needs one or more processor simulator plugins. These are not included with standard VMs. The plugins are only built in one’s own VM builds if the support libraries are built. See the bochsx86, bochsx64, gdbarm32, and gdbarm64 directories at the top levels of building subdirectories, e.g. building/linux64x64/{bochsx86,bochsx64,gdbarm32,gdbarm64}. These have makeem scripts in them. Only the macos64 scripts are used with any regularity.So to simulate a Cog VM- build the support libraries for the processors you want to use for your platform- make a squeak.cog.spur VM For your platform- use this VM to build/run your VMMaker imageThe standard VMs
Thank you for the explanation! We now got it working and I was able to run a BouncingAtomsMorph in the simulator morph. :-)
Cool :-) Less than a decade ago Dan Ingalls said at a meeting in Palo Alto that the VM JIT simulator was running about the same speed as the Alto :-)
Improving the docs could indeed be helpful for newbies such as us. Maybe we
can add some more explicit pointers on this soon. I'm leaving it up to you to keep this issue open until this has been achieved :)
Well, if we do it together I can scribe accurately and you can say what needs to be said.
— Reply to this email directly, view it on GitHub https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/711#issuecomment-2790641689, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADY5VUDDXMUFMOQIZLMGAQL2YVTRRAVCNFSM6AAAAAB2UR2CF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJQGY2DCNRYHE . You are receiving this because you commented.Message ID: @.***>
-- ,,,^..^,,, best, Eliot