Hacker News Reader

The problem with valgrind is that they don't update it often enough. Is once a year enough?

Why does it need to be updated? Valgrind is that rare piece of software that always has been working absolutely flawlessly for me.

If you wish to use new CPU features such as the imaginary AVX-1337, have fun waiting a year before being able to run your leak check.

And no, I don't want to maintain multiple code paths on my system, even for compiled generated AVX[2,512,SSE4.1] code. If you do so, you end up having a dev system unrepresentative of the production one.

If nothing else, it needs to be updated for various new syscalls/x86 instructions periodically on the different platforms it supports (if you've never tried running valgrind on something that isn't Linux, you might not have run into this.)

Reply on news.ycombinator.com