|
From: Russ C. <rs...@sw...> - 2004-04-06 18:56:50
|
Just installed valgrind 2.1.1-2 using Debian testing apt-get. tux=; valgrind ls fix_auxv: we didn't see enough auxv entries (seen=0) tux=; Is this likely to be a Debian problem or did they just get a bad version of Valgrind? I searched the valgrind-users archives on sourceforge for fix_auxv but found nothing. Apologies if this has been recently discussed. Russ |
|
From: Tom H. <th...@cy...> - 2004-04-06 19:44:49
|
In message <407...@sw...>
Russ Cox <rs...@sw...> wrote:
> Just installed valgrind 2.1.1-2 using Debian testing apt-get.
>
> tux=; valgrind ls
> fix_auxv: we didn't see enough auxv entries (seen=0)
> tux=;
Is that with a 2.2 kernel by any chance? That's the only way I know
to provoke that message at present.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: Russ C. <rs...@sw...> - 2004-04-06 21:09:52
|
Tom Hughes wrote: > Is that with a 2.2 kernel by any chance? That's the only way I know > to provoke that message at present. So it is! I played funny games tricking the Debian/stable installer into installing a Debian/testing system, but apparently I missed the kernels. I'll upgrade my kernel. Thanks. Russ |