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...<br>
<br><div>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...)</div>
<div><br></div><div>HTH,</div><div>David</div><div><br><div class="gmail_quote">On Tue, Nov 4, 2008 at 8:33 AM, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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<br>
'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.<br>
<br>
Thanks for any hints,<br>
Dominik<br>
_______________________________________________<br>
ParaView mailing list<br>
<a href="mailto:ParaView@paraview.org" target="_blank">ParaView@paraview.org</a><br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
</blockquote></div><br></div>