<div class="gmail_quote">On Sun, Nov 6, 2011 at 08:02, 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;">
<div id=":2rc">I did not mean building on Windows, I meant developing on Windows<br>
(only C/C++). I.e. doing regular everyday boring stuff like debugging<br>
crashes or deadlocks, testing memory accesses with valgrind...</div></blockquote><div><br></div><div>We both understood that. Alexander says he uses the VS debugger, for example.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":2rc"> If you<br>
tell me that all the main developers do not use Windows it sounds<br>
quite pessimistic...</div></blockquote><div><br></div><div>You are welcome to contribute.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div id=":2rc">
Yes, valgrind-equivalent tool is what I care for<br>
most.</div></blockquote><div><br></div><div>Valgrind is a pretty unique tool. You could try the commercial software called Purify. There is nothing preventing Microsoft from contributing valgrind support for Windows.</div>
</div>