[postgis-devel] Segfault with Intersects() in 1.0.6-CVS

Carl Anderson carl.anderson at vadose.org
Fri Dec 2 19:44:03 PST 2005


Benj Carson wrote:

Benj,

I tried your test and got a FALSE, validly, back.
my env
select version();
 PostgreSQL 8.1.0 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.0.1 
20050727 (Red Hat 4.0.1-5)

select postgis_full_version();
 POSTGIS="1.0.4" GEOS="2.1.4" PROJ="Rel. 4.4.9, 29 Oct 2004" USE_STATS 
DBPROC="0.3.0" RELPROC="0.3.0"

Although some precision errors at very similar numeric values can still 
be encountered your test example would never result in an error in a 
working PostGIS version. 

There must be a cross linked LIB or a Postgresql function stub pointing 
to an earlier version.

I also note that
   postgis_full_version() returns version 1.0.4
you reference
   version 1.0.5
and
   version 1.0.6-CVS

hinting at version problems.

C.
 

>Here are my full versions:
>
>POSTGIS="1.0.4" 
>GEOS="2.1.4" 
>PROJ="Rel. 4.4.9, 29 Oct 2004" 
>USE_STATS 
>DBPROC="0.3.0" 
>RELPROC="0.3.0"
>
>Debian currently has not packaged libgeos-2.2.0 yet.  If you think it will 
>help I can go and compile 2.2.0 however.
>
>Thanks,
>
>
>Benj
>
>
>
>
>
>
>On December 2, 2005 06:44 pm, Paul Ramsey wrote:
>  
>
>>The key information here is your geos version, actually:
>>
>>select postgis_full_version();
>>
>>P
>>
>>On 2-Dec-05, at 4:20 PM, Benj Carson wrote:
>>    
>>
>>>Hello,
>>>
>>>I am getting segfaults with PostGIS 1.0.6-CVS (updated as of
>>>2005-12-02) and
>>>PostgreSQL 8.1 (from Debian) when calling Intersects():
>>>
>>># select intersects(
>>>    polygonfromtext('POLYGON((0.0 0.0,1.0 0.0,1.0 1.0,1.0 0.0,0.0
>>>0.0))'),
>>>    polygonfromtext('POLYGON((0.0 2.0,1.0 2.0,1.0 3.0,0.0 3.0,0.0
>>>2.0))')
>>>  );
>>>
>>>server closed the connection unexpectedly
>>>        This probably means the server terminated abnormally
>>>        before or while processing the request.
>>>
>>>
>>>Hopefully you are aware of this problem; if so please ignore me.
>>>Otherwise,
>>>I thought I should let you kind folks know.  Now, I know that CVS
>>>code is
>>>sometimes unstable, but I was using 1.0.5 but it was crashing on
>>>ExteriorRing() for me, so I thought I'd see if 1.0.6-CVS had solved my
>>>problem (it did), but I then ran into this...
>>>
>>>Let me know if you need more info.
>>>
>>>Thanks,
>>>
>>>
>>>Benj Carson
>>>_______________________________________________
>>>postgis-devel mailing list
>>>postgis-devel at postgis.refractions.net
>>>http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>>      
>>>
>>_______________________________________________
>>postgis-devel mailing list
>>postgis-devel at postgis.refractions.net
>>http://postgis.refractions.net/mailman/listinfo/postgis-devel
>>    
>>
>_______________________________________________
>postgis-devel mailing list
>postgis-devel at postgis.refractions.net
>http://postgis.refractions.net/mailman/listinfo/postgis-devel
>  
>




More information about the postgis-devel mailing list