MantisBT
Mantis Bug Tracker Workflow

View Revisions: Issue #30581 All Revisions ] Back to Issue ]
Summary 0030581: Modeling Data - Standard_OutOfRange within Geom_BSplineSurface::LocateV()
Revision 2019-03-16 11:35 by kgv
Description Geom_BSplineSurface::LocateV() does not properly check array bounds leading to Standard_OutOfRange in some cases, but this check is disabled at beginning of file.

Test case perf/modalg/bug26443_1 triggers this scenario.
It also produces unstable screenshots, which might be caused by reading undefined out-of-range values.

Note that function BSplCLib::Hunt() might return result outside of array range.
In particular, this happens for very close values, which are probably occur due to serialization issues (e.g. model has been once saved in text .brep format).
It looks reasonable adding first/last values with some tolerance.
From other side, almost all existing BSplCLib::Hunt() calls clamps result to a valid range anyway.
Revision 2019-03-16 11:12 by kgv
Description Geom_BSplineSurface::LocateV() does not properly check array bounds leading to Standard_OutOfRange in some cases.

Note that function BSplCLib::Hunt() might return result outside of array range.
In particular, this happens for very close values, which are probably occur due to serialization issues (e.g. model has been once saved in text .brep format).
It looks reasonable adding first/last values with some tolerance.
From other side, almost all existing BSplCLib::Hunt() calls clamps result to a valid range anyway.
Revision 2019-03-16 09:29 by kgv
Description Geom_BSplineSurface::LocateV() does not properly check array bounds leading to Standard_OutOfRange in some cases.


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker