Hi all, I was able to upgrade a 5.1 image all the way to update #420 (17325), thanks to the helpful new-ish methods in MCMcmUpdater. Should I be able to upgrade beyond that? When I try to apply #421, I get a friendly offer to drop into an emergency evaluator. One time a dialog box appeared, informing me that the VM has crashed. I thought I grabbed a screenshot of the VM crash dialog, but I guess I didn't. I do have a crash.dmp file. System details: 32-bit Windows 7 VMs tried: squeakcog.spur_win32x86_201803080952 and cog_win32x86_squeak.cog.spur_201608171728 Updates being applied at time of crash: update-mt.421.mcm (I was also unable to update a 5.1 image via trunk past some point on OS X without a crash. It might have been this update there too, but I don't have the details to confirm for now.) Thanks, |
On Mar 19, 2018, at 12:10 AM, Tim Johnson wrote: > Updates being applied at time of crash: > > update-mt.421.mcm > System-mt.963 > > (I was also unable to update a 5.1 image via trunk past some point > on OS X without a crash. It might have been this update there too, > but I don't have the details to confirm for now.) > Yes. Crash duplicated in the following configuration: * OS X 10.12.6 * fresh 5.1 64-bit image * Cog Spur VM 64-bit 2018-03-08-0952 Again, while trying to apply update #421 after applying all updates up to and including #420. THanks, TIm |
In reply to this post by Tim Johnson-2
Hi Tim, try "Smalltalk cleanUp: true" before applying update #421. Best, Marcel
|
In reply to this post by Tim Johnson-2
Hi Tim,
On Mon, Mar 19, 2018 at 11:30 AM, Tm Jhnsn <[hidden email]> wrote:
I cannot reproduce this on 10.10.5 using a VM built from the latest sources. We don't have all builds succeeding right now and so don't have a new release on binary but are working to resolve this asap. THanks, _,,,^..^,,,_ best, Eliot |
In reply to this post by Tim Johnson-2
Hi Tim,
On Mon, Mar 19, 2018 at 11:30 AM, Tm Jhnsn <[hidden email]> wrote:
Which image precisely? * Cog Spur VM 64-bit 2018-03-08-0952 _,,,^..^,,,_ best, Eliot |
In reply to this post by Eliot Miranda-2
Hi Tim,
On Tue, Mar 20, 2018 at 10:30 AM, Eliot Miranda <[hidden email]> wrote:
Belay that. I realize I have to set the update map to trunk before it'll see significant updates.
_,,,^..^,,,_ best, Eliot |
In reply to this post by marcel.taeumel
Hi Marcel,
Thanks! That helped. I was able to update to #421 after running this. Should this message be sent as a postamble script or preload script or somesuch? Now unfortunately the (64-bit image on OS X) locks up (no crash) at update-nice.422.mcm, "Installing Kernel-nice.1127". :) In SqueakDebug.log, there is the following: MessageNotUnderstood: TextMorph>>currentHand For the record: it has been very useful to upgrade the MonticelloConfigurations package to the latest version, so I have the ability to send e.g. MCMcmUpdater default doUpdateUpTo: 421 Thanks again, Tim On 2018-03-20 09:50, Marcel Taeumel wrote: > Hi Tim, > > try "Smalltalk cleanUp: true" before applying update #421. > > Best, > Marcel > >> Am 19.03.2018 08:11:05 schrieb Tim Johnson <[hidden email]>: >> >> Hi all, >> >> I was able to upgrade a 5.1 image all the way to update #420 (17325), >> thanks to the helpful new-ish methods in MCMcmUpdater. Should I be >> able to upgrade beyond that? >> >> When I try to apply #421, I get a friendly offer to drop into an >> emergency evaluator. One time a dialog box appeared, informing me >> that the VM has crashed. I thought I grabbed a screenshot of the VM >> crash dialog, but I guess I didn't. I do have a crash.dmp file. >> >> System details: >> >> 32-bit Windows 7 >> 32-bit image, starting with 5.1 and upgraded via trunk through >> update-420 >> >> VMs tried: squeakcog.spur_win32x86_201803080952 and >> cog_win32x86_squeak.cog.spur_201608171728 >> >> Updates being applied at time of crash: >> >> update-mt.421.mcm >> System-mt.963 >> >> (I was also unable to update a 5.1 image via trunk past some point on >> OS X without a crash. It might have been this update there too, but I >> don't have the details to confirm for now.) >> >> Thanks, >> Tim |
Hi, A full dump of SqueakDebug.log follows. This is from trying to update from #421 to #422, and the lockup occurs at update-nice.422.mcm, "Installing Kernel-nice.1127". It seems the lock up was indeed the result of a "system error. VM: Squeak 5.0, Cog Spur VM 5.0-201803080952 Note that the debug log below states my image is "Squeak6.0alpha" but that is because the image is renamed as such by one of the trunk updates. The original image was in fact originally "Squeak5.1-16549-64bit" as downloaded from squeak.org. I would guess that if the current target is actually Squeak5.2 then there is cause to revisit whichever update renames the image. :) SqueakDebug.log: MessageNotUnderstood: TextMorph>>currentHand MessageNotUnderstood: TextMorph>>currentHand On 2018-03-20 11:06, Tim Johnson wrote:
|
Hi Tim,
On Tue, Mar 20, 2018 at 11:20 AM, Tim Johnson <[hidden email]> wrote:
Good. I'm off the hook :-) Your subject line is misleading; this is a lock up, not a VM crash. On Mac OS X I see the lock up but see no VM crash. Does it help that you can start from the 6.0alpha download (6.0alpha) instead of starting from scratch?
_,,,^..^,,,_ best, Eliot |
In reply to this post by Tim Johnson-2
macOS 10.13.4 beta 5 (17E182a) running on Squeak.cog.spur_macos64x64_201803080952.app from bintray <https://bintray.com/opensmalltalk/vm/cog/201803080952#files>.
Ken G. Brown
|
In reply to this post by Eliot Miranda-2
On 2018-03-20 11:32, Eliot Miranda wrote:
> Hi Tim, > > On Tue, Mar 20, 2018 at 11:20 AM, Tim Johnson <[hidden email]> wrote: > >> Hi, >> >> A full dump of SqueakDebug.log follows. This is from trying to update >> from #421 to #422, and the lockup occurs at update-nice.422.mcm, >> "Installing Kernel-nice.1127". It seems the lock up was indeed the >> result of a "system error. VM: Squeak 5.0, Cog Spur VM >> 5.0-201803080952 >> >> Note that the debug log below states my image is "Squeak6.0alpha" but >> that is because the image is renamed as such by one of the trunk >> updates. The original image was in fact originally >> "Squeak5.1-16549-64bit" as downloaded from squeak.org. > > Good. I'm off the hook :-) Your subject line is misleading; this is a > lock up, not a VM crash. On Mac OS X I see the lock up but see no VM > crash. Does it help that you can start from the 6.0alpha download > (6.0alpha) instead of starting from scratch? Whoops! I'm sorry Eliot. The one time the Win32 VM actually popped up a dialog window (instead of an in-image offer to drop to evaluator), it suggested there had been a VM problem. I could never repeat the pop-up of that dialog window, though. Thanks... I will be more careful about my terminology. Re: the 6.0 alpha image -- this becomes a catch-22. :D I was playing around with updating via trunk to see if I could get around the unaccounted-for removal of Context>>#inspectorClass present in the downloadable 6.0alpha image. But now I see it is present after updating through trunk too. May be time for me to cease and desist. Thanks, Tim |
Free forum by Nabble | Edit this page |