Segfault when meshing a Torus

[jeromerobert]

See the source code to reproduce this bug at:
http://groups.google.com/group/oce-dev/browse_thread/thread/20b05eb496a7eb9e/dfa5786377563d10

This post was about OCCT 6.5. The output of the test program is a bit different with OCCT 6.5.1/OCE 0.6:
With the patch: https://gist.github.com/1258872
Without the patch: https://gist.github.com/1258842

Bug status with different versions:

• OCC 6.5 without patch: Very large mesh and sefault at radius 17.
• OCC 6.5 with patch: Good mesh size, no sefault
• OCC 6.5.1 / OCE 0.6 without patch: The mesh size is small and constant. Segfault at radius 17.
• OCC 6.5.1 / OCE 0.6 with patch: Good mesh size. Segfault at radius 17.

The mesh size problem has been fixed by OCCT 6.5.1, but the segfault has not. This bug has been register by OCC as OCC22445. (http://www.opencascade.org/org/forum/thread_20486). I guess it's still concidered as open as it's not in the OCCT 6.5.1 releases notes.

[dbarbier]

The segfault happens because mesher fails, your nbTriangle() method should end with:

   return pt.IsNull() ? 0 : pt->NbTriangles();

[tpaviot]

Issue reproduced and added to the unittest suite, see commit f9964f7.

[ghost]

BRepMeshTestSuite.testMeshTorus passes and according to OCCT, this issue was fixed in 6.5.3: http://tracker.dev.opencascade.org/view.php?id=22445 , closing.