<div dir="ltr">Hi Chris,<div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 24, 2017 at 3:40 PM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"> <br><div dir="ltr">After trying a fairly recent VM, I've actually had to go back to that Aug-17-2016 VM, because of the frequency of crashes in the new VM. Have the very latest latest VM's fixed these crashes? We might want to do some testing before making it the one the world sees..</div></blockquote><div><br></div><div>My understanding is that the VM source as per VMMaker.oscog-eem.2187, 27 March 2017, 3 pm, git commit 4ceff23323bcd0f2d3d0a4a43c2995<wbr>f43d09c98a, Mon Mar 27 16:07:32 2017 should be good. This fixed what I hope is the remaining bug with the new compactor at snapshot. I certainly don't experience crashes using it, and I hear from some members of the Pharo community that it works well. That said, Levente reported a crash on update in the 64-bit VM as of <span style="color:rgb(0,0,0);font-size:12.800000190734863px">VMMaker.oscog-eem.2197 , git commit date</span><span style="color:rgb(0,0,0);font-size:12.800000190734863px"> 201704181925. I haven't been able to reproduce this yet, and I haven't seen any problems with update in my usage.</span></div><div><span style="color:rgb(0,0,0);font-size:12.800000190734863px"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 20, 2017 at 2:01 PM, Fabio Niephaus <span dir="ltr"><<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail-m_-5914100143411544688gmail-m_720583734326468298m_8780329025596267553m_8723924612273733460GmSign">Hi Chris,</div><span><div class="gmail-m_-5914100143411544688gmail-m_720583734326468298m_8780329025596267553m_8723924612273733460GmSign"><br></div><div class="gmail-m_-5914100143411544688gmail-m_720583734326468298m_8780329025596267553m_8723924612273733460GmSign">On Wed, Apr 19, 2017 at 6:57 PM Chris Cunningham <<a href="mailto:cunningham.cb@gmail.com" target="_blank">cunningham.cb@gmail.com</a>> wrote:<br></div></span><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span>Over the last week, I've been trying to build a new image on the latest trunk, which for my purposes needs to include ODBC, and until just recently, I've been failing.<div><br></div><div>After rooting around a bit, I finally found that the base trunk image I was using (from this location: <a href="http://files.squeak.org/6.0alpha/" target="_blank">http://files.squeak.<wbr>org/6.0alpha/</a> ) seems to all be based off of this VM:</div></span><div><img src="cid:ii_15b87136f0e9a556" alt="image.png" style="max-width: 100%;"><br></div><span><div> My previous image that I was porting from is:</div></span><div><img src="cid:ii_15b8712f5f458bd1" alt="image.png" style="max-width: 100%;"><br></div><span><div>which worked fine calling out FFI/ODBC.</div><div>After trying many changes (looking at 64 bit image, 32 bit image, other fumbling around), I finally tracked down a current VM from </div><div><a href="https://bintray.com/opensmalltalk/vm/cog/_latestVersion#files" style="font-size:12.8px" target="_blank">https://bintray.com/opensmallt<wbr>alk/<span class="gmail-m_-5914100143411544688gmail-m_720583734326468298m_8780329025596267553m_8723924612273733460m_46629657905190686gmail-il">vm</span>/cog/_latestVersion#file<wbr>s</a><br></div><div>This version:</div></span><div><img src="cid:ii_15b87221fdc0d06e" alt="image.png" style="max-width: 100%;"><br></div><span><div>seems to work just fine with FFI (at leat, it runs the ODBC code without a hitch). Even in the 64 bit version.</div><div><br></div><div>I've sent this message for a few reasons:</div><div>1 - for my future self, to remember where the link is for the most current VM's (I can't find a link to it elsewhere outside of the email archives)</div></span></div></blockquote><div><br></div><div>I've added the link to the vm section at: <a href="http://squeak.org/downloads/" target="_blank">http://squeak.org/downloads/</a><br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>2 - for anyone else having FFI issues</div><div>3 - as a subtle request to eventually update the stable, blessed version of the VMs that are used in the bleeding edge Image archives, so that they work better with less hassle.</div></div></blockquote><div><br></div></span><div>I'm afraid we still don't have a good release process in place.</div><div>However, I'm happy to update the vm used for the Squeak trunk bundles with a current bleeding edge vm if no one objects.</div><div><br></div><div>Best,</div><div>Fabio</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Thanks,</div><div>cbc</div></div>
<br>
</blockquote></div></div>
<br><br>
<br></blockquote></div><br></div></div>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail-m_-5914100143411544688gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>
</div></div>