calltree (0.9.6) depends on valgrind 2.0.0
however, there is already valgrind 2.1.0 available
this is causing cyclic upgrade/downgrade of valgrind
wouldn't it be better if portage would report this circular dependency rather then repeatedly upgrade/downgrade the packages when doing emerge -u world ?
A fix would be to add calltree 0.9.7 to the gentoo portage.
It supports valgrind 2.0.0, 2.1.0, 2.1.1
calltree 0.9.6 only supports 2.0.0
i just wonder -> currently i have valgrind 2.1 and calltree 0.9.6 -> and valgrind seems to be working fine ?
but i'm just doing a basic stuff (checking for memory errors and leaks, only --check-leak cmdline option, nothing special)
what's the problem with running calltree 0.9.6 with valgrind 2.1 ? may i get wrong results ?
For me, the usage of valgrind 2.1.0 and calltree 0.9.6 results in:
# calltree ls
Tool and core interface versions do not match.
Interface version used by core is: 5.0
Interface version used by tool is: 4.0
The major version numbers must match
You need to at least recompile, and possibly update,
your skin to work with this version of Valgrind.
latest valgrind and calltree should have this fixed (~x86 currently)
looks good for me !
looks good for me as well