<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 23, 2016 at 11:21 AM, marcel.taeumel <span dir="ltr"><<a href="mailto:Marcel.Taeumel@hpi.de" target="_blank">Marcel.Taeumel@hpi.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="h5"><br>
</div></div>Hi, there.<br>
<br>
It is, unfortunately, not possible to turn back time and rewrite history. ;-)<br></blockquote><div><br></div><div>... unless we're dealing with software. Oh wait, we are ;)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">There is several important code that makes excessive use of instVar<br>
accesses such as in SystemProgressMorph or HandMorph. Making any change in<br>
their class layout while using some of their methods will provoke a strange<br>
error. This could only be changed by a VM that keeps old class<br>
layouts/schemata around for some longer time until there is no old compiled<br>
method on any stack anymore.</blockquote><div><br></div><div>Class layout changes and instance migration is handled fully in the image by class ClassBuilder. The VM is not at fault here.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Usually, restarting the update process helps here. There is no way to fix<br>
that in order to interactively update from 5.0 to 5.1 without any errors.<br></blockquote><div><br></div><div>We can retroactively change the config map that introduced the problem. I'm certain it would be possible to fix, but I am not entirely sure it's worth the trouble.</div><div><br></div><div>- Bert - </div></div></div></div>