BRepTools::Dump and lots of crashes

I'm trying to use the BRepTools::Dump function to display info about some shapes during debugging. Unfortunately, the program always crashes at the line of code with Dump. I'm basically using the Bottle tutorial without MFC, which I've adapted to my needs.

I've searched for an answer on the forum, but found a lot of contradictory information.
- for some people it works without any problems (clearly not the case here).
- some suggested that I should compile the program in the "Release" configuration. I did that, but now the program does not even execute (complains about a missing entry point to some library that seems to be in the Qt distribution).
- some suggested that the OCC libraries should be re-compiled with the debug option. This takes about 9 hours on my machine, so I'd like to get it right from the start.

I know I can use BRepTools::Write(shape, "path\to\file"), but the result is in Brep format which is quite un-friendly to human inspection.

So, what is the way to use the Dump function? What should I re-compile and with what options? Even better, is there some other function or pieces of software that I can use to inspect TopoDS_Shape's?


Thomas Paviot's picture


I remember I also faced this issue a few months ago. The problem was that I used MSVC9 with precompiled binaries of OCC6.3.0 provided from this website (which are compiled with MSVC7). I recompiled OCC6.3.0 with MSVC9 and that solved the problem.

If you don't want to reompile OCC by yourself, OCC6.3.0 precompiled binaries for MSVC9 are available from the pythonOCC project download area: (this file was contributed by Sébastien Ramage).

Best Regards,


Tiberiu Chelcea's picture

Hi Thomas,

thanks for the clarification. I am using MSVC9, so maybe this will solve it. The funny thing is that I've compiled my own libraries, but I've used gcc4.4 (from the MinGW suite), it took forever. This was the recommended way to compile it. I'll try to install it and see how it goes.


Tiberiu Chelcea's picture

It works, thanks!!! One thing: if you want to do development, you have to copy the 'inc' directory from the full OCC version (usually $OCC_HOME/ros/inc) into the new one. The full version includes all sorts of links with 3rd party tools, which I don't need now, so there's lots of saved space too.