Smalltalk › Squeak › Squeak VM

Re: [squeak-dev] 11 June Building report (2)

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Eliot Miranda-2

Re: [squeak-dev] 11 June Building report (2)

On Sun, Jun 12, 2011 at 3:51 AM, Edgar J. De Cleene <[hidden email]> wrote:

On 6/11/11 5:35 PM, "Eliot Miranda" <[hidden email]> wrote:

Hi Edgar,

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.

HTH
Eliot

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

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.

Edgar

Chris Muller-3

Re: [squeak-dev] 11 June Building report (2)

> 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.

Thanks for the explanation. One mini-issue I bump up against on
Windows is the name of the executable. I can set up file-association
for .image to associate to squeak.exe (for the interpreter VM) or
Croquet.exe for Cog.

I ended up associating to squeak.exe and renaming Croquet.exe,
Croquet.ini, and Croquet.map to squeak.exe, squeak.ini and squeak.map.
Everything seems to run fine, but will the map file work in this case
or do you see any other potential problems about doing this?

- Chris

Eliot Miranda-2

Re: [squeak-dev] 11 June Building report (2)

On Wed, Jun 15, 2011 at 9:36 AM, Chris Muller <[hidden email]> wrote:

> 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.

Thanks for the explanation. One mini-issue I bump up against on
Windows is the name of the executable. I can set up file-association
for .image to associate to squeak.exe (for the interpreter VM) or
Croquet.exe for Cog.

I ended up associating to squeak.exe and renaming Croquet.exe,
Croquet.ini, and Croquet.map to squeak.exe, squeak.ini and squeak.map.
Everything seems to run fine, but will the map file work in this case
or do you see any other potential problems about doing this?

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.

best

Eliot

- Chris