[ms4w-users] Re: [ka-Map-users] Crash with Gmap demo

[Jeff McKenna]

once again: please please please please please always respond to the 
mailing list.

I recommend you try MS4W 2.1 with the 4.9 upgrade package, and see if 
you get the same error.

jeff



Jeff Dege wrote:
> MS4W 2.0 - with the MapServer 4.9 Upgrade.
> 
>> -----Original Message-----
>> From: ka-map-users-bounces at lists.maptools.org 
>> [mailto:ka-map-users-bounces at lists.maptools.org] On Behalf Of 
>> Jeff McKenna
>> Sent: Wednesday, August 09, 2006 10:47 AM
>> To: ka-map-users
>> Subject: Re: [ka-Map-users] Crash with Gmap demo
>>
>> As I said, please always respond to the list.
>>
>> Can you provide which exact MS4W version you are using? (2.1, or
>> 1.5.5...kinda thing)
>>
>> jeff
>>
>>
>> Jeff Dege wrote:
>>> Same error, same place.
>>>
>>> Crashes with gmap75.map, does not with gmap75_wms.map. 
>>>
>>>> -----Original Message-----
>>>> From: ka-map-users-bounces at lists.maptools.org 
>>>> [mailto:ka-map-users-bounces at lists.maptools.org] On Behalf Of 
>>>> Jeff McKenna
>>>> Sent: Wednesday, August 09, 2006 7:08 AM
>>>> To: ka-map-users
>>>> Subject: Re: [ka-Map-users] Crash with Gmap demo
>>>>
>>>> well first you should be using gmap_ms4w_ms48.zip from the MS4W 
>>>> downloads page: 
>>>> http://www.maptools.org/ms4w/index.phtml?page=downloads.html
>>>>
>>>> and if you have the same problem please let the list know.
>>>>
>>>> jeff
>>>>
>>>>
>>>>
>>>> Jeff Dege wrote:
>>>>> I'm trying to get the ka-map-0.2 demo running with gmap-ms46.
>>>>>
>>>>> I configured everything as described, and got a crash in 
>>>> php-cgi.exe:
>>>>>   The instruction at "0x77fcd977" referenced memory at 
>> "0x00000038".
>>>>> The memory could not be "written".
>>>>>
>>>>> Gmap-ms46 comes with a number of map files, so I tried editing
>>>>> kamap\include\config.php to reference gmap75_wms.map, instead of
>>>>> gmap75.map, and it worked.
>>>>>
>>>>> So made a copy of gmap75_wms.map (which worked), and did a 
>>>> diff against
>>>>> gmap75.map (which didn't) and proceeded to change one 
>> line at a time
>>>>> until I had the minimum difference that triggered the crash.
>>>>>
>>>>> There are two.
>>>>>
>>>>> In gmap75.map (which doesn't work), I find:
>>>>>
>>>>>   #
>>>>>   # Start of web interface definition
>>>>>   #
>>>>>   WEB
>>>>>     MINSCALE 2000000
>>>>>     MAXSCALE 50000000
>>>>>   #
>>>>>   # On Windows systems, /tmp and /tmp/ms_tmp/ should be 
>>>> created at the
>>>>> root 
>>>>>   # of the drive where the .MAP file resides.
>>>>>   #
>>>>>     IMAGEPATH "/ms4w/tmp/ms_tmp/" 
>>>>>     IMAGEURL "/ms_tmp/"
>>>>>   #  LOG "/tmp/gmap.log"
>>>>>   END
>>>>>
>>>>>
>>>>> In my gmap75_test.map (which does work), I have:
>>>>>
>>>>>   #
>>>>>   # Start of web interface definition
>>>>>   #
>>>>>   WEB
>>>>>     MINSCALE 2000000
>>>>>     MAXSCALE 50000000
>>>>>   #
>>>>>   # On Windows systems, /tmp and /tmp/ms_tmp/ should be 
>>>> created at the
>>>>> root 
>>>>>   # of the drive where the .MAP file resides.
>>>>>   #
>>>>>     IMAGEPATH "/ms4w/tmp/ms_tmp/" 
>>>>>     IMAGEURL "/ms_tmp/"
>>>>>   END
>>>>>
>>>>>   PROJECTION
>>>>>     "init=epsg:42304"
>>>>>   END
>>>>>
>>>>> If I remove the PROJECTION section from my gmap75_test.map, 
>>>> I get the
>>>>> crash.  Or if I add the commented-out LOG line in the WEB 
>>>> section, I get
>>>>> the crash.
>>>>>
>>>>> This is using a freshly-installed kmap_0.2_ms4w.zip and 
>>>> gmap_ms46.zip.
>>>>> On Windows, using the ms4w of Mapserver 4.9.
>>>>>
>>>>> It has all the signs of being a random memory stomp - unitialized
>>>>> variables, somewhere in the php executable or the 
>> php_mapscript.dll.
>>>>>
>>>>>