[Paraview] release/debug modes in MSVC

Dominik Szczerba dominik at itis.ethz.ch
Tue Nov 4 09:25:39 EST 2008

Thanks a lot David for the clarifications,

David Cole wrote:
> If you want to debug things with the Microsoft compiler on Windows, you 
> have to build *everything* loaded into the process as a "Debug" 
> configuration. It is worth the extra time taken to do this. Otherwise, 
> you will simply have mysteries on your hands and you will spend 
> countless hours pulling your hair out trying to figure out why something 
> is crashing when there is clearly nothing wrong with the source code...
> Mismatches between Debug and Release are just simply not a good idea 
> with the Microsoft compiler. (Because the Debug/Release variants of the 
> runtime libraries have different structures associated with memory 
> allocations and allocating in one while deallocating in the other 
> frequently leads to disaster...)
> HTH,
> David
> On Tue, Nov 4, 2008 at 8:33 AM, Dominik Szczerba <dominik at itis.ethz.ch 
> <mailto:dominik at itis.ethz.ch>> wrote:
>     Configuring with cmake, is it possible - other than hacking - to use
>     Release builds for VTK or PV *and* Debug mode for my own stuff? On
>     linux I can easily do that (with different CMAKE_BUILD_TYPE's), but
>     on Windows it seems in order to debug my own stuff I have to compile
>     the whole VTK / PV in debug mode, which I dont need/want - this is
>     particularly annoying with PV long compilation times. Selecting
>     'Debug' as the build mode looks for libraries in bin\Debug.
>     Unfortunately, just copying is not smart enough - I get mysterious
>     crashes tracing back nowhere.
>     Thanks for any hints,
>     Dominik
>     _______________________________________________
>     ParaView mailing list
>     ParaView at paraview.org <mailto:ParaView at paraview.org>
>     http://www.paraview.org/mailman/listinfo/paraview

More information about the ParaView mailing list