You are not logged in.
------- Additional Comment #2 From Tom Hughes 2008-06-12 08:51 -------
You appear to be using valgrind 3.3.0 on a gibc 2.8 system but 3.3.1 does not support glibc 2.8 and configure should have errored at build time. What you are seeing is valgrind not having suppressions for glibc 2.8 issues.
This is a quote from a bug I reported regarding valgrind.
I'm using the testing repository, but maybe it should have given a conflict? Anyway, seems valgrind is releasing a new version compatible with glibc 2.8.
Link to the bug report http://bugs.kde.org/show_bug.cgi?id=163852
EDIT: I also think he mean that 3.3.0 doesnt support glibc 2.8 ![]()
Last edited by raul_nds (2008-06-12 14:31:13)
Offline
This might be valuable information for valgrind maintainer, so use arch bug tracker for that.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
I already reported a bug in the valgrind bug tracker.
The thing is that glibc in testing is always released before valgrind do their release that supports the latest glibc.
If you don't enable the testing repo eveything should be fine (as always).
I will contact the package maintainer to let him know.
Offline
See this :
http://valgrind.org/docs/manual/dist.news.html
It mentions glibc 2.8 support.
valgrind 3.3.1 is in extra now.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline