Description:
valgrind 3.3.0 currently doesn't support glibc 2.8, but 3.3.1 will, says the valgrind developers. The thing is glibc 2.8 is already in testing, so when you run valgrind, it will spit a bunch of non-existing errors (non-existing on your program at least).

Bug report here http://bugs.kde.org/show_bug.cgi?id=163852

I think this already happened when glibc 2.6 was released, at least from what I saw in the forums. (http://bbs.archlinux.org/viewtopic.php?id=36309)

To solve this I think that when upgrading glibc for those who have testing enable, a conflict should prevent glibc from being upgraded, because valgrind doesn't support it. This way:

1. Who really uses valgrind, my guess is, won't upgrade glibc until valgrind is updated
2. Those who don't use valgrind will remove it temporarily, so they can upgrade glibc.

Remember, these are only suggestions :)

Cheers

Raul



Steps to reproduce:
just run any program (hello world .e.g) with valgrind, and errors will come up