[Vm-dev] [squeak-dev] Older VM's won't start the latest beta images
marcel.taeumel at hpi.de
Mon May 30 09:57:22 UTC 2022
Hi Dave --
See https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/638 [https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/638]
Should we fix this in the image or in the VM?
Am 30.05.2022 11:48:03 schrieb Marcel Taeumel <marcel.taeumel at hpi.de>:
Hi Dave --
I wonder why I cannot change the format from 68021 to 68533 via
CompiledCode multipleBytecodeSetsActive: true.
Smalltalk snapshot: true andQuit: true.
Any ideas? At least the System Reporter does not report that format. Is this a VM bug?
Am 29.05.2022 16:04:04 schrieb David T. Lewis <lewis at mail.msen.com>:
On Sun, May 29, 2022 at 08:06:59AM +0000, Jaromir Matas wrote:
> I wonder what?s changed that the images starting from Squeak6.0beta-21772-64bit on won?t start with the previous release VM (squeak.cog.spur_win64x64_202003021730) or even with pre-release new VMs (e.g. version 3154).
> I?m on Win10, the process explorer (windows) shortly runs WerFault.exe and than the Squeak process is closed/disappears.
The change is here:
The current release candidate image does not have this, but it will be
applied as soon as you update that image, and it expected to be part of
the final release. The update applies a new image format number to the
saved image files (stored in the first 4 bytes of the image file) when
multiple bytecode set support is required from the VM. Effectively, the
means that the image is using the Sista bytecode set. Older VMs can
run the Sista bytecodes but do not yet have the code for recognizing
the additional image format number.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev