<div dir="ltr">Hi Stéph,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jun 13, 2014 at 4:38 AM, Stéphane Rollandin <span dir="ltr"><<a href="mailto:lecteur@zogotounga.net" target="_blank">lecteur@zogotounga.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I got a crash right away with newest cogwin when opening my usual working image. No simple case easy to reproduce yet. Dump is attached.<br>
</blockquote><div><br></div><div>Thanks. This is fixed in VMMaker.oscog-eem.772. It was an overzealous bounds check on a relocated call of an interpreter primitive. The VM complained and aborted because the interpreter primitive;s address was out of the code zone (as of course it should be; it is in the interpreter) i.e. the VM should not have performed the check and should not have exited. Apologies. I'll be building and uploading new VMs soon.</div>
</div><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>