Hi Marc,<div><br></div><div>Thank you so much for having a look.<br><div><br><div class="gmail_quote">2013/1/3 Marc Feeley <span dir="ltr">&lt;<a href="mailto:feeley@iro.umontreal.ca" target="_blank">feeley@iro.umontreal.ca</a>&gt;</span><br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I can&#39;t reproduce this bug with OpenBSD 5.2 and the g++ 4.2.1 which comes with it.  My guess is that the problem is related to a bug in the versions of g++ you have used.  Can you install an older g++ and see if that solves the problem?  Can you also try to compile using gcc (i.e. don&#39;t use --enable-cplusplus)?<br>

</blockquote><div><br></div><div>Aha funny.</div><div><br></div><div>Just for reference, in the test you made, was the OS compiled for the AMD64 architecture?</div><div><br></div><div><br></div><div>I did not use 5.2 but &quot;current&quot; a.k.a. &quot;snapshot&quot; for AMD64, as found on <a href="http://www.mirrorservice.org/pub/OpenBSD/snapshots/amd64/">http://www.mirrorservice.org/pub/OpenBSD/snapshots/amd64/</a> . Except for regarding exiting Gambit, this version of the system has shown to perfectly stable in every way I checked, so this is why I was so surprised to see any issue about Gambit&#39;s execution on it.</div>

<div><br></div><div>And right, I tried with <span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px">G++ 4.7.2 and 4.6.3. On your 5.2 installation, installing this would look something like:</span></div>

<div><span style="background-color:rgb(255,255,255);color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px"><br></span></div></div></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>

<div class="gmail_quote"><div><font face="courier new, monospace"><span style="background-color:rgb(255,255,255)"><font color="#222222">PKG_PATH=</font></span><font color="#222222"><a href="http://www.mirrorservice.org/pub/OpenBSD/5.2/packages/amd64/">http://www.mirrorservice.org/pub/OpenBSD/5.2/packages/amd64/</a></font></font></div>

</div></div></div><div><div class="gmail_quote"><div><font face="courier new, monospace"><font color="#222222">pkg_add </font>g++-4.6.3p6</font></div></div></div><div><div class="gmail_quote"><div><br></div></div></div><div>

<div class="gmail_quote"><div>(or just <font face="courier new, monospace">pkg_add <a href="http://www.mirrorservice.org/pub/OpenBSD/5.2/packages/amd64/g++-4.6.3p6.tgz">http://www.mirrorservice.org/pub/OpenBSD/5.2/packages/amd64/g++-4.6.3p6.tgz</a></font> )</div>

<div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">rm /usr/bin/g++</font></div><div><font face="courier new, monospace">ln -s /usr/local/bin/eg++ /usr/bin/g++</font></div></div>

</div></blockquote><div><div class="gmail_quote"><div><br></div><div>I believe I did not try 4.2.1 til now because ./configure warned me that that GCC version is broken or slow or something.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

[..]<div class="im">&gt; But if so, why is not an uncaught exception error printed at gsc termination on every platform (which is g++&#39;s default behavior)???<br>
<br>
</div>No, the runtime system should catch this exception in the ___BEGIN_TRY / ___END_TRY macros which are called in lib/setup.c (in only 2 places, so it should be easy to verify that the exception is actually caught by adding some printfs in the code).<br>

</blockquote><div><br></div><div>Right, so that&#39;s really funny.</div><div><br></div><div><br></div><div><div><br></div><div>Quite soon I&#39;ll try compiling Gambit on the 5.2 and maybe snapshot with different versions of both GCC and G++ including 4.2.1, and report the results here.</div>

</div><div><br></div><div><br></div><div>Best regards,</div><div>Mikael</div><div><br></div></div></div>