<br><br><div class="gmail_quote">On Wed, Jun 15, 2011 at 9:36 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com">asqueaker@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 class="im"><br>
> 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.<br>
<br>
</div>Thanks for the explanation. One mini-issue I bump up against on<br>
Windows is the name of the executable. I can set up file-association<br>
for .image to associate to squeak.exe (for the interpreter VM) or<br>
Croquet.exe for Cog.<br>
<br>
I ended up associating to squeak.exe and renaming Croquet.exe,<br>
Croquet.ini, and Croquet.map to squeak.exe, squeak.ini and squeak.map.<br>
Everything seems to run fine, but will the map file work in this case<br>
or do you see any other potential problems about doing this?<br></blockquote><div><br></div><div>There should be no problems. The VM computes the name of the .map file from the name of the executable. Renaming all three is indeed the right thing to do.</div>
<div><br></div><div>best</div><div>Eliot</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888"><br>
- Chris<br>
</font></blockquote></div><br>