2015-03-02 18:04 GMT+01:00 mathog <mathog@...1176...>:
On 01-Mar-2015 12:01, Krzysztof Kosiński wrote:
I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
Not me! Command line gdb is fine for me anyway. A more pressing issue is that I could never find a decent substitute for valgrind, so it wasn't possible to look for memory issues on the Windows version that can be found on Linux. Dr. Memory appeared to have promise. Unfortunately the last time I tried it, almost 2 years ago, Inkscape wouldn't run in it. I don't recall what the problem was, just that it was a no go.
Another option is to use Address Sanitizer / Thread Sanitizer present in newer GCC. It has a lot lower overhead, though it won't catch memory leaks.
Stack Overflow says that deleaker can be used on Windows instead of Valgrind.
Regards, Krzysztof