2010/4/18 Jelle Feringa <jelleferi...@gmail.com> > > You can try to use the OCC6.3.0 library compiled in debug mode (the > > one provided from the official website was compiled in release mode). > > So far I haven't ran into situations where I needed to resolve to a > debugger. > I would say that in this case trying to use a debugger is creating > more problems than it might be able to resolve... >
You're right, but I far as I know the use of a C++ debugger is the only way "to get a stacktrace from a segfault" if the segfault comes from OCC. I would recommend you to step through the code with a python debugger > rather than a C++ debugger. > ( ipdb is terrific for this since it offers tab completion... ) > The use of a python debugger rather enables to find the best way to use the OCC library : it's a more 'pragmatic' approach, but also empirical. We definitely chose this one in the pythonocc development. > This method allows you to test lots of possibilities in a very short > time... > Though I do think the tolerance your setting is not reasonable for > most CAD kernels... > Can you go further with this interesting argument? What is, according to you, a "reasonable tolerance for a CAD kernel"? Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
