[postgis-users] GEOS crashing PostgreSQL?
Tyler Mitchell
tylermitchell at shaw.ca
Tue Oct 24 22:32:33 PDT 2006
> On Tue, Oct 24, 2006 at 09:53:09PM -0600, Michael Fuhr wrote:
>> I saw that ptarray_from_GEOSCoordSeq() was passing a size_t *
>> as the second argument to GEOSCoordSeq_getSize() and
>> GEOSCoordSeq_getDimensions(), but those functions expect
>> unsigned int *.
>
> I see that this has changed between GEOS 2.2 and 3.0. My 64-bit
> build uses GEOS 2.2, where the abovementioned functions expect
> unsigned int *. In GEOS 3.0 they expect size_t *.
Are you saying that v3.0 should already work? I just tried the patch
against the SVN version and it now passed regress_ogc. It was
failing for me before.
Where did I read a note about someone fixing this problem already for
64bit?
Thanks for the patch - it made my day :) Can any of the dev. team
confirm whether or not we need this and get it rolled in somehow?
Cluelessly yours,
Tyler
More information about the postgis-users
mailing list