Now that glibc-2.19 is stabling, we'll need a version that compiles against it. I have been using valgrind 3.9.0 pretty regularly on a couple machines for the last six months without any issues. Reproducible: Always
Arch teams please stabilize =dev-util/valgrind-3.9.0 for KEYWORDS="amd64 arm x86" Note: ppc and ppc64 will skip.
I wonder if valgrind needs strict < deps on glibc version to prevent incompatible updates. Or at least more aggressive stabilization of valgrind versions. It is no fun for stable users when reverse deps are broken by stablizations and left in broken state for weeks on end. Valgrind needs to be rebuilt after any glibc update to work correctly. It's not just a problem for new installs, existing working stable setups get broken by world update. That doesn't sound very stable at all!
x86 stable
amd64 stable
arm stable, closing