New Compilation of mapserv Throwing "double free" Error - SOLVED

[Bill Thoen]

Yes, it's Linux, and you've put your finger on the problem. Turns out I had
two versions of the GEOS shared library linked to my last build of the GDAL
code. Thanks to Frank Warmerdam for looking into it and pointing that out,
I just deleted the old library and rebuilt GDAL, an everything's cool now.
I don't know how that happened, but once we found the problem, it was an
easy fix.

Here's what the evidence looked like:
[warmerdam at localhost bin]$ ldd /usr/local/bin/ogrinfo | grep geos
        libgeos-3.0.0rc2.so => /usr/local/lib/libgeos-3.0.0rc2.so
(0x00002aaaab0d2000)
        libgeos_c.so.1 => /usr/local/lib/libgeos_c.so.1
(0x00002aaaab31c000)
        libgeos-3.0.0rc3.so => /usr/local/lib/libgeos-3.0.0rc3.so
(0x00002aaaab42c000)


On Wed, Dec 20, 2006 at 09:25:05PM -0600, Steve Lime wrote:
> I assume this is Linux distribution, which one? Is OGR also compiled
> with GEOS support? I wonder if there could be a conflict allocating
> global GEOS objects by each system. One thing to try would be to compile
> MapServer with GEOS but without GDAL/OGR and do a mapserv -v again.
> 
> Steve
> 
> >>> Bill Thoen <bthoen at GISNET.COM> 12/20/06 8:54 AM >>>
> I just compiled Mapserver from source and all seemed to go okay, but 
> when I tested it with the -v switch I got this:
> 
> # ./mapserv -v
> MapServer version 4.10.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP 
> OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=FREETYPE SUPPORTS=WMS_SERVER 
> SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT 
> SUPPORTS=WCS_SERVER SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS 
> INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
> *** glibc detected *** ./mapserv: double free or corruption (fasttop): 
> 0x00000000005dd940 ***
> ======= Backtrace: =========
> /lib64/libc.so.6[0x305426d313]
> /lib64/libc.so.6(__libc_free+0x84)[0x305426d494]
> /usr/local/lib/libgeos-3.0.0rc3.so[0x2aaaab88eea1]
> /lib64/libc.so.6(__cxa_finalize+0x8e)[0x3054231e0e]
> /usr/local/lib/libgeos-3.0.0rc3.so[0x2aaaab83c613]
> ...followed by a long memory map....
> 
> Does anyone have a suggestion about what I should do to correct this?
> 
> Thanks,
> - Bill Thoen
>