[geos-devel] [GEOS] #894: FreeBSD and MacOSX failures on 3.7.0 - group: geos::geom::CoordinateArraySequenceFactory, test: test<1> assertion failed

GEOS geos-trac at osgeo.org
Mon Aug 27 19:52:33 PDT 2018


#894: FreeBSD and MacOSX failures on 3.7.0 - group:
geos::geom::CoordinateArraySequenceFactory, test: test<1> assertion failed
------------------------+---------------------------
 Reporter:  robe        |       Owner:  geos-devel@…
     Type:  defect      |      Status:  new
 Priority:  blocker     |   Milestone:  3.7.0
Component:  Default     |     Version:  master
 Severity:  Unassigned  |  Resolution:
 Keywords:              |
------------------------+---------------------------

Comment (by robe):

 More notes from gdt on mailing list

 https://lists.osgeo.org/pipermail/geos-devel/2018-August/008490.html

 {{{
 I don't see this on NetBSD/7 amd64, which uses gcc 4.8.

 I did a build on macos 10.11, which uses clang (but a similar Intel
 processor):

   Apple LLVM version 8.0.0 (clang-800.0.42.1)
   Target: x86_64-apple-darwin15.6.0
   Thread model: posix
   InstalledDir: /Library/Developer/CommandLineTools/usr/bin

 and get the same failure as the bug.

 Specifically, if I run test 1 in that group, it fails:

   $ ./geos_unit geos::geom::CoordinateArraySequenceFactory 1
   ===============================
     GEOS Test Suite Application
   ===============================

   geos::geom::CoordinateArraySequenceFactory: [1=F]

   ---> group: geos::geom::CoordinateArraySequenceFactory, test: test<1>
        problem: assertion failed

   tests summary: failures:1 ok:0

 but tests 2,3,4,5 all pass.

 The test is in tests/unit/capi/GEOSGeomFromWKBTest.cpp in the sources, and
 is doing:

         // POINT(1.234 5.678)
         std::string wkt("POINT (1.234 5.678)");
         std::string wkb("01010000005839B4C876BEF33F83C0CAA145B61640");
         test_wkb(wkb, wkt);

 I don't know how to get it to produce the mismatching content; the
 --verbose option in --help is unrecognized, and I can't see how it would
 be reading the driver source.

 So I wonder if something in geos is sensitive to gcc/clang differences.
 (Vastly less likely, there could be a clang bug.)


 }}}

-- 
Ticket URL: <https://trac.osgeo.org/geos/ticket/894#comment:6>
GEOS <http://trac.osgeo.org/geos>
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite (JTS).


More information about the geos-devel mailing list