[postgis-devel] [PostGIS] #1668: ST_AsText, ST_AsEWKT under Windows 64-bit PostGIS 64-bit is all screwy

[PostGIS]

#1668: ST_AsText, ST_AsEWKT under Windows 64-bit PostGIS 64-bit is all screwy
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  high     |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:  mingw64  |  
---------------------+------------------------------------------------------

Comment(by robe):

 Wouldn't it be better practice to check if a buffer can store a value
 before you write to the buffer? This code seems pretty lazy and hard to
 follow in my opinion becasue you have to know that vasprintf is expected
 to return the length even if it can't write the value.

 Anyrate with this change (which I guess I should be using sizeof or
 something similar instead), topology passes with flying colors, raster
 (the rt_pixelvalue error has gone) away so I'm left with the same 3
 failures as I have in 32-bit.  One gnawing issue is after the cunit tests
 of postgis, it crashes trying to start the postgres tests. Another is
 raster testapi is giving funny messages about l not valuid, but then comes
 back with "tests all successful" so not sure what to make of that.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1668#comment:14>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.