<br><br><div class="gmail_quote">On Sun, Jun 12, 2011 at 3:51 AM, Edgar J. De Cleene <span dir="ltr"><<a href="mailto:edgardec2005@gmail.com">edgardec2005@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class="im">
<font size="4"><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt"><br>
<br>
<br>
On 6/11/11 5:35 PM, "Eliot Miranda" <<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>> wrote:<br>
<br>
</span></font></font><blockquote><font size="4"><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Hi Edgar,<br>
<br>
if you included Croquet.map then the C stack backtrace would be more informative. Looks like its crashing in perform:, which may indicate heap corruption.<br>
<br>
HTH<br>
Eliot<br>
</span></font></font></blockquote></div><font size="4"><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt"><br>
<br>
<br>
Sure I miss something, so please tell how to use Croquet.map, the file i have reads Aug 18 2010 as date modified so seems not used by the test<br></span></font></font></div></blockquote><div><br></div><div>The .map file contains the addresses of all functions in the WIndows VM. The VM uses this file to annotate its C stack backtrace when it crashes. If you look in the cogwin.zip files I produce on my site you'll see there is always a Croquet.map file with every Croquet.exe. So do keep the two together and deploy with the map file if you want good stack backtraces from Cog VMs on Windows.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><font size="4"><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt"><font color="#888888">
<br>
Edgar</font></span></font></font>
</div>
<br><br>
<br></blockquote></div><br>