Valgrind Release 3.9.0
valgrind.org
valgrind.org
I write C on a non-valgrind capable platform. It's literally scary what you missed when you take what you think is working properly and throw it through valgrind.
As a result, I developed a lot of defensive habits to ward off these types of problems, such that I don't make those mistakes very often anymore. But once in a while, I still get weird errors, and the first thing I try is running it under valgrind.
Bing, bang, problem found, fixed. I may be not too far off the mark in saying that valgrind may have saved C and C++.
Apple should probably employ someone full-time to support valgrind on OS X, just for the in-house benefits...
http://clang.llvm.org/docs/AddressSanitizer.html
It catches more stuff than valgrind, and only slows a program down to ~half normal speed.
It requires compile time instrumentation, but I'm usually ok with that.
In any case, several basic features of the previous version of Valgrind work on OSX 10.8/10.9, so I don't think it is correct to say Valgrind is useless on OS X.
It would be more useful if you explained the specific problems with Valgrind on OSX that force you to use Linux.
If you heavily depend on non-core tools, yes. Otherwise, though, for 99% of developers it was install-reboot-resume work — and the advantages of being able to test what your users use are significant as well.
Awesome. There was no good way to write suppressions for those. I'm glad this got done.
Memory corruption errors are hard to find and I'd love a tool that helped me find them. Systematic leaks (app leaks over hours or days) would also be good to find. I've had zero luck with valgrind. Always had to resort to finding them the old-fashioned way.
I do wish it was further along though, I haven't seen much change in the month or so I've been working through it :(