Hi all.
I recently updated my debian unstable to a new libc6 (problems started
with 2.10.1-6) and I get a bunch of new errors from memcheck. When I
compile the following (and obviously anything else):
int main() {
return 0;
}
and let memcheck run with it, I get a huge amount of this:
...
Am 16.11.2009 09:37, schrieb Tom Hughes:
On 16/11/09 08:12, Andre Naujoks wrote:
Is it possible for you guys to push a newer valgrind version with this
warning to the debian mirrors?
You're asking the wrong people - you need to talk to whoever maintains
the debian package of valgrind.
I will do that, or at least try to convince them to set libc6-dbg as a
dependency of valgrind.
afaics, libc6-dbg is a suggests of valgrind package.
please, open a bug report and request libc6-dbg promotion to
recommends (at least).
you can also discuss the issue with aurelien jarno (debian
Hi!
I ran into exactly the same problem. What I found out is that valgrind needs to
be aware of the version of glibc you are using.
Corollary: if you update glibc, you have to recompile valgrind. If the
maintainer forgot to do so, you have to do it yourself.
Did it myself and the errors are
Hi.
There was no need to recompile valgrind. Only the install of libc6-dbg was
needed. After that, all was fine with both the debian valgrind and the one
from svn.
Regards
Andre
Am 16.11.2009 10:39, schrieb markus.kli...@elektrobit.com:
Hi!
I ran into exactly the same problem. What I
On Mon, Nov 16, 2009 at 11:35 AM, Andre Naujoks nauts...@googlemail.comwrote:
There was no need to recompile valgrind. Only the install of libc6-dbg was
needed. After that, all was fine with both the debian valgrind and the one
from svn.
The Debian maintainers have to recompile Valgrind such
