[postgis-devel] [Internet] Re: Postgis 2.4.6 regession tests fails on Solaris

[Dechaux Eric CEN (BCQ STIG)]

Using gdb is out of my knowledge. As using clang and Solaris compiler, 
the first won't build and the second is not properly supported with most 
build toolchains.


For now, the only thing I am able to do is run the test manually, which 
give me unexpected result :

# select postgis_full_version();
postgis_full_version
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  POSTGIS="2.4.6 r17068" PGSQL="100" GEOS="3.7.1-CAPI-1.11.1 27a5e771" 
PROJ="Rel. 5.2.0, September 15th, 2018" GDAL="GDAL 2.3.3, released 
2018/12/14" LIBXML="2.9.4" LIBJSON="0.12" RASTER
(1 row)

# select 'POINT(10 4)'::geometry, 'POINT(10 5)'::geometry;
                   geometry                  | geometry
--------------------------------------------+--------------------------------------------
  000000000140240000000000004010000000000000 | 
000000000140240000000000004014000000000000
(1 row)



# select postgis_addbbox('POINT(10 4)'::geometry), 'POINT(10 4)'::geometry;
               postgis_addbbox               | geometry
--------------------------------------------+--------------------------------------------
  000000000140240000000000004010000000000000 | 
000000000140240000000000004010000000000000
(1 row)


# select 'POINT(10 4)'::geometry = 'POINT(10 5)'::geometry;
  ?column?
----------
  t
(1 row)


# select postgis_addbbox('POINT(10 4)'::geometry) = 'POINT(10 4)'::geometry;
  ?column?
----------
  f
(1 row)


I think the tests results are OK


Le 21/01/2019 à 16:30, Greg Troxel a écrit :
> "Darafei \"Komяpa\" Praliaskouski" <me at komzpa.net> writes:
>
>> Given the rarity of architecture I suggest you to rebuild with PostGIS 2.5
>> - we've fixed many things for supporting ARM/MIPS and may happen that your
>> sparcv9 will just catch up. We didn't have any SPARC for testing and didn't
>> know of any install on SPARC until today. Please send the patches if you'll
>> figure them out.
> I used to test on sparc.  I will again someday; I have both a sparc64
> and a 32-bit sparc.
>
> I think it's important to keep an eye on odd platforms.  Often bugs that
> show up there are real bugs that happen not to express on amd64.   But I
> certainly understand about limited resources.
>
> I have seen some failures on NetBSD/arm (earmv7hf-el specifically) with
> gcc 5, I think in geos, but so far I am suspicious of the compiler.
>
> I would suggest that the OP run 'paranoia' on their system to check the
> floating point support, and also build with -O0 as there could be
> compiler bugs.
>
> Another thing is to try clang instead of gcc, or a sun compiler.
>
> You could also try to run various sanitizers under clang.  It's possible
> postgis has code that invokes undefined behavior which happens to be ok
> on intel (or it would have been fixed :-).
>
> sparc uses IEEE754 so that should not be an issue (vs vax which has
> floating point that is different).  But, note the part in the mips bug
> about different valid representations of nan and hex equivalence checks
> not being sound.
>
>
> The other thing to do is to begin to trace the troublesome functions
> with gdb.
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel

-- 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: avertissement.txt
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20190121/193a9263/attachment-0001.txt>