[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: valgrind: doesn't start (cannot allocate memory)

> Furthermore, I cannot reproduce this bug by using a current version of
> prelink from unstable -- I can neither recreate the error message you got
> while running valgrind, nor recreate the error message you got when trying
> to un-prelink /usr/lib/valgrind/stage2.  I suspect that your broken stage2
> binary was created by an older version of prelink, but I'm reassigning this
> bug to prelink (and downgrading it) so that someone more familiar with
> prelink than I am can try to confirm this.

Actually, valgrind versions prior to 2.2.0-1 had a bug when they
were prelinked so this can be the problem. You can try to purge
valgrind and reinstall it again from unstable, ensuring that 
/usr/lib/valgrind is completely removed after purging.

Andrés Roldán

CSO - Fluidsignal Group S.A.		aroldan@fluidsignal.com
Debian Developer - The Debian Project   aroldan@debian.org

Mobile: +57 300-7920981
GPG F/P: 0EE9 27C9 55F1 92E4 3809  B852 D8E0 724B B293 96EB

Attachment: pgpxwqdpruerD.pgp
Description: PGP signature

Reply to: