Static string in WKBReader causes glibc errors when Geos is statically linked

[yvesdaemen]

I am statically linking Geos against my own C program. This program runs without problems, except until the very end when a glibc errors occurs.

I have traced this back to the static string BAD_GEOM_TYPE_MSG. When I remove the static modifier and initialise the string inside the constructor, everything goes well.

I did not get this error when linking dynamically, but Valgrind complained about an invalid free. This is probably the same thing, only my program did not crash on it.

[mloskot]

yvesdaemen,

Isn't it a duplicate of ticket #231 ?

[yvesdaemen]

Yes,

I've had some problems submitting the report. Sorry for the duplicate, you can reject one of them ;-)

[pramsey]

Can you attach a test program? Otherwise it is unlikely anyone will take the time to first create an example program before working up a general solution. Even better, attach a general purpose patch.

[pramsey]

If I receive a patch, I will apply it.

[mwtoews]

I think this bug also affects the python bindings. See:  http://lists.osgeo.org/pipermail/geos-devel/2009-May/004174.html

[pramsey]

strk, any chance you can take a look at this one? If you fix in trunk I'll pull the patch back.

[strk]

I can build GEOS trunk statically. If anyone has problem and time to give feedback feel free to reopen.

[pramsey]

Also found in trunk by DFuhry:

 http://lists.osgeo.org/pipermail/geos-devel/2009-July/004270.html

[pramsey]

Fixed in 3.0 at r2614

Fixed in 3.1 at r2615

Fixed in trunk at r2616