[squeak-dev] Image not startable after save

Jakob Reschke forums.jakob at resfarm.de
Sun May 24 15:41:33 UTC 2020


The failure is introduced when I load Graphics-mt.432.

More specifically, I see these changes:
DisplayScreen class>>shutDown (removed)
DisplayScreen class>>startUp (removed)
DisplayScreen>>restore (changed)
DisplayScreen>>shrink
DisplayScreen>>shutDown (removed)
Graphics package postscript (changed)

It fails after I load either of these:
DisplayScreen class>>startUp (removed)
Graphics package postscript (changed)

The rest of the changes I can load without breaking the image.

Am Fr., 22. Mai 2020 um 18:36 Uhr schrieb Jakob Reschke
<forums.jakob at resfarm.de>:
>
> This is from the image before the update, the VM is the same (should
> be the 5.3 release VM if I remember correctly):
>
> Image
> -----
> C:\Users\Jakob\HiDrive\Squot-trunk-64bit.2.image
> Squeak6.0alpha
> latest update: #19634
> Current Change Set: Git unit of work
> Image format 68021 (64 bit)
>
> Virtual Machine
> ---------------
> C:\Squeak\VMs\Squeak64\Squeak64.exe
> Open Smalltalk Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-nice.2715]
> Win32 built on Mar  3 2020 08:36:19 GMT Compiler: 4.2.1 Compatible
> Clang 8.0.1 (tags/RELEASE_801/final)
> platform sources revision VM: 202003021730
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Mon Mar 2
> 18:30:55 2020 CommitHash: 6a0bc96 Plugins: 202003021730
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git
> CoInterpreter VMMaker.oscog-nice.2715 uuid:
> 78e2f556-9829-42fe-963d-e19dfc43c0e9 Mar  3 2020
> StackToRegisterMappingCogit VMMaker.oscog-eem.2719 uuid:
> e40f3e94-3a54-411b-9613-5d19114ea131 Mar  3 2020
>
> Am Fr., 22. Mai 2020 um 18:33 Uhr schrieb Jakob Reschke
> <forums.jakob at resfarm.de>:
> >
> > Hi all,
> >
> > I just updated my Squeak trunk image. After saving, I cannot reload it:
> >
> > ---------------------------
> > Squeak!
> > ---------------------------
> > Aborting!!!!
> > Color depth 0 not supported
> > ---------------------------
> > OK
> > ---------------------------
> >
> > Then it prints the stack trace and exits.
> >
> > I restored a backup from yesterday and reloaded my own changes. An
> > image saved from that is still functional. After updating Squeak
> > again, I see the same error as above, so it is reproducible.
> >
> > But I cannot invoke the error with a fresh image... so it must be
> > something with my image after all. Any ideas or suggestions? Does
> > anyone else experience issues after an update?
> >
> > Kind regards,
> > Jakob


More information about the Squeak-dev mailing list