[postgis-devel] Issue 147 in postgis: regress_ogc_prep fails with PostgreSQL crash
codesite-noreply at google.com
codesite-noreply at google.com
Wed Apr 8 05:27:50 PDT 2009
Comment #4 on issue 147 by Sandro.Santilli: regress_ogc_prep fails with
PostgreSQL crash
http://code.google.com/p/postgis/issues/detail?id=147
I've transferred the test to the unit testing of GEOS for capi and here's
what I get:
==3513== Invalid read of size 8
==3513== at 0x4ECDDFD:
geos::geom::prep::PreparedPolygonContainsProperly::containsProperly(geos::geom::Geometry
const*) (PreparedPolygonContainsProperly.cpp:58)
==3513== by 0x4ECE0EE:
geos::geom::prep::PreparedPolygon::containsProperly(geos::geom::Geometry
const*)
const (PreparedPolygonContainsProperly.h:73)
==3513== by 0x518D95B: GEOSPreparedContainsProperly_r
(geos_ts_c.cpp:3799)
==3513== by 0x50165B: void
tut::test_object<tut::test_capigeospreparedgeometry_data>::test<2>()
(GEOSPreparedGeometryTest.cpp:108)
==3513== by 0x504147:
tut::test_group<tut::test_capigeospreparedgeometry_data,
50>::run_test_seh_(void
(tut::test_object<tut::test_capigeospreparedgeometry_data>::*)(),
tut::test_group<tut::test_capigeospreparedgeometry_data,
50>::safe_holder<tut::test_object<tut::test_capigeospreparedgeometry_data>
>&)
(tut.h:973)
==3513== by 0x504430:
tut::test_group<tut::test_capigeospreparedgeometry_data,
50>::run_test_(std::_Rb_tree_iterator<std::pair<int const, void
(tut::test_object<tut::test_capigeospreparedgeometry_data>::*)()> > const&,
tut::test_group<tut::test_capigeospreparedgeometry_data,
50>::safe_holder<tut::test_object<tut::test_capigeospreparedgeometry_data>
>&)
(tut.h:899)
==3513== by 0x504F18:
tut::test_group<tut::test_capigeospreparedgeometry_data,
50>::run_next() (tut.h:862)
==3513== by 0x40C1D6:
tut::test_runner::run_all_tests_in_group_(std::_Rb_tree_const_iterator<std::pair<std::string
const, tut::group_base*> >) const (tut.h:452)
==3513== by 0x40BACE: main (tut.h:398)
==3513== Address 0x5efda80 is 0 bytes inside a block of size 136 free'd
==3513== at 0x4C2514D: operator delete(void*) (vg_replace_malloc.c:342)
==3513== by 0x4ECDDF3:
geos::geom::prep::PreparedPolygonContainsProperly::containsProperly(geos::geom::Geometry
const*) (PreparedPolygonContainsProperly.cpp:57)
==3513== by 0x4ECE0EE:
geos::geom::prep::PreparedPolygon::containsProperly(geos::geom::Geometry
const*)
const (PreparedPolygonContainsProperly.h:73)
==3513== by 0x518D95B: GEOSPreparedContainsProperly_r
(geos_ts_c.cpp:3799)
I attach the tester, if anyone feels like trying with an older snapshot.
I don't think I touched anything related, so my bet is this is a memory
error
which results in random bugs.
Attachments:
GEOSPreparedGeometryTest.cpp 2.3 KB
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
More information about the postgis-devel
mailing list