id summary reporter owner description type status priority milestone component version resolution keywords cc 1754 in_gml regress check crashes on vc++ 64 edb (only 9.3) robe robe "I guess I had neglected to do make check against edb builds and was doing it on my compiled versions. Sadly I'm seeing a lot of crashes here -- though not sure if much can be done about it. On 9.1.3 VC++ compiled (note mingw64 is more or less okay except for the rounding issues) {{{ PostgreSQL 9.1.3, compiled by Visual C++ build 1500, 64-bit Postgis 2.0.0 - r9605 - 2012-04-04 15:31:29 GEOS: 3.3.3-CAPI-1.7.4 PROJ: Rel. 4.8.0, 6 March 2012 Running tests loader/Point ....................... ok loader/PointM ....................... ok loader/PointZ ....................... ok loader/MultiPoint ....................... ok loader/MultiPointM ....................... ok loader/MultiPointZ ....................... ok loader/Arc ....................... ok loader/ArcM ....................... ok loader/ArcZ ....................... ok loader/Polygon ....................... ok loader/PolygonM ....................... ok loader/PolygonZ ....................... ok loader/TSTPolygon ......... ok loader/TSIPolygon ......... ok loader/TSTIPolygon ......... ok loader/PointWithSchema ..... ok loader/NoTransPoint ......... ok loader/NotReallyMultiPoint .... failed (wkt test: diff expected obtained: /tmp/ pgis_reg/test_18_diff) loader/MultiToSinglePoint ... failed ( wkt test: running shp2pgsql output: /tmp /pgis_reg/loader.err) loader/ReprojectPts .... failed ( wkt test: running shp2pgsql output: /tmp/pgis _reg/loader.err) loader/ReprojectPtsGeog .... failed ( wkt test: running shp2pgsql output: /tmp/ pgis_reg/loader.err) loader/Latin1 .... ok binary .. ok regress .. ok regress_index .. ok regress_index_nulls .. ok lwgeom_regress .. ok regress_lrs .. ok removepoint .. ok setpoint .. ok simplify .. ok snaptogrid .. ok summary .. ok affine .. ok empty .. ok measures .. ok legacy .. ok long_xact .. ok ctors .. ok sql-mm-serialize .. ok sql-mm-circularstring .. ok sql-mm-compoundcurve .. ok sql-mm-curvepoly .. ok sql-mm-general .. ok sql-mm-multicurve .. ok sql-mm-multisurface .. ok polyhedralsurface .. ok polygonize .. ok postgis_type_name .. ok out_geometry .. ok out_geography .. ok in_gml .. failed (diff expected obtained: /tmp/pgis_reg/test_52_diff) in_kml .. failed (diff expected obtained: /tmp/pgis_reg/test_53_diff) iscollection .. failed (diff expected obtained: /tmp/pgis_reg/test_54_diff) regress_ogc .. failed (diff expected obtained: /tmp/pgis_reg/test_55_diff) regress_ogc_cover .. failed (diff expected obtained: /tmp/pgis_reg/test_56_diff ) regress_ogc_prep .. failed (diff expected obtained: /tmp/pgis_reg/test_57_diff) regress_bdpoly .. failed (diff expected obtained: /tmp/pgis_reg/test_58_diff) regress_proj .. failed (diff expected obtained: /tmp/pgis_reg/test_59_diff) regress_management .. failed (diff expected obtained: /tmp/pgis_reg/test_60_dif f) dump .. ok dumppoints .. ok wmsservers .. ok wkt .. ok wkb .. ok tickets .. ok typmod .. ok remove_repeated_points .. ok split .. ok relate .. ok bestsrid .. ok concave_hull .. ok hausdorff .. ok regress_buffer_params .. ok offsetcurve .. ok relatematch .. ok isvaliddetail .. ok sharedpaths .. ok snap .. ok node .. ok unaryunion .. ok clean .. ok relate_bnr .. ok in_geojson .. ok uninstall .. ok (3857) Run tests: 85 Failed: 13 make: *** [check] Error 13 }}} The in_gml one is the result of a crash. I suspect a lot of the others that follow are server trying to stand back up from crahs. I vaguely remember having this issue with my 32-bit build before but can't recall if we changed something to fix the issue and it was a memory leak. Raster looks good though comes thru with flying colors on both vc++ and mingw64 pg :) " defect closed medium PostGIS 2.1.0 postgis 2.0.x fixed mingw64,windows 64bit,history