MantisBT
Mantis Bug Tracker Workflow

View Revisions: Issue #26308 All Revisions ] Back to Issue ]
Summary 0026308: Segmentation fault in BSplCLib::LocateParameter
Revision 2015-07-09 14:48 by nbv
Steps To Reproduce ReadStep D_First Face.stp
XGetOneShape rr D_First
explode rr f
mksurface ss rr_1

svalue ss -1.427997381773311e+018 4.512451574816904e+016 xx yy zz

dump xx yy zz

*********** Dump of xx *************
-5.42659125962715e+207

*********** Dump of yy *************
2.90803974424011e+209

*********** Dump of zz *************
-3.1731154470359e+207
Revision 2015-07-09 14:46 by nbv
Steps To Reproduce ReadStep D_First Face.stp
XGetOneShape rr D_First
explode rr f
mksurface ss rr_1

svalue ss -1.427997381773311e+018 4.512451574816904e+016 xx yy zz

dump xx yy zz
Revision 2015-06-03 14:32 by BenjaminBihler
Steps To Reproduce I have attached a STEP file containing one face. If the face has been read in, then these lines

---------------------------------

TopoDS_Face face = ...

gp_Pnt point;

std::cout << "Computing point." << std::endl;
BRep_Tool::Surface(face)->D0(-1.427997381773311e+018, 4.512451574816904e+016,
point);
std::cout << "Finished computation." << std::endl;

---------------------------------

lead to the described Valgrind error and debugging situation as described above on my Linux 32 machine. The crashes on Windows 64 are sporadic, therefore I cannot give definite information about that, but when a crash appeared it was close to such a call to D0 with extreme u and v values.


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker