calltree is needed by Kcachegrind. The current ebuild is hardwired via the DEPEND="=dev-util/valgrind-2.0.0" and causes the valgrind ebuild to ping pong between versions 2.0.0 and 2.1.0 on every world update. This depend should be changed to DEPEND=">=dev-util/valgrind-2.0.0". Reproducible: Always Steps to Reproduce: 1. 2. 3.
This version of calltree (the newest actually) does not support valgrind-2.1.0 and fails in the configure script when using emerge with --nodeps, so the DEPEND is correct. Actually the interface changed between valgrind-2.0.0 and valgrind-2.1.0 so even binary calltree does not work.
So this bug is invalid
If Calltree does not work with Valgrind 2.1.0, then shouldn't there be a block on upgrading from Valgrind 2.0.0 to Valgrind 2.1.0. The current behavior is a world update ping pongs between the two valgrind versions. That does not seem to be correct behavior. Should this be a calltree ebuild bug or a Valgrind ebuild bug?
It is a known missing feature in portage. The easiest workaround is to make sure that valgrind is not in your world file. That will prevent the flipping