Bug in intersect_classify_common_impl.hpp (performFaceLoopWork)

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Take the tarball in the attachment, extract the content, correct the 
Makefile (specifying location of libcarve and Carve) and compile (make).
2. Run any of the two examples. In the failed_carve_example case, several runs 
might be needed, to produce the error (carve::exception). another_example 
normally takes only one or two runs to produce the same exception.
3. I realised there is a potential bug in intersect_classify_common_impl.hpp - 
break; missing at the end of POINT_ON case in the switch in function 
performFaceLoopWork. If you insert the missing break, rebuild Carve and run the 
examples, you get into new problem: FACE LOOP ERRORs. Those occur in the same 
cases, where there was an exception before (so whenever there is a POINT_ON 
case in the switch). The curious thing is that this is not deterministic 
(occurs on different places in different runs although the input is the same 
every time - or it even doesn't occur in some cases).

What is the expected output? What do you see instead?
All described above. I would expect to have 1 closed manifold in the end.

What version of the product are you using? On what operating system?
Latest Carve version from repository. I'm using gcc version 4.1.2 20080704 (Red 
Hat 4.1.2-44).

Please provide any additional information below.

I give two examples, as the first one (failed_carve_example) uses only Carve 
functions (including Carve/common things), but only produces exceptions rarely, 
while the other example (another_example) uses the new function makeSphere 
(feel free to include it to geometry.cpp, btw) and produces exception more 
often.

Original issue reported on code.google.com by mpe...@gmail.com on 20 Aug 2010 at 11:32

Attachments:

• failed_carve_example.tar.gz

[GoogleCodeExporter]

I have the same problem as described above. (step 3)

Are there ways to fix the problem?

Thanks

Original comment by ho...@gmx.de on 27 Sep 2012 at 4:36

[GoogleCodeExporter]

Has there been any fix to this, I have the same problem

Original comment by SRLock...@gmail.com on 18 Jul 2013 at 3:52