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

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



reassign 288640 prelink
severity 288640 important
tags 288640 unreproducible
thanks

Hi Christian,

The bug you reported against valgrind does not seem to be a bug in valgrind;
if it only happens when prelink is run over the binaries, then this would be
a prelink bug, not a valgrind bug.

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.

To fix your immediate problem with valgrind, you can reinstall the package
(apt-get install --reinstall valgrind).  Please save a copy of the files
/usr/lib/valgrind/{stage2,valgrind} before you do this, in case they're
needed to further debug the problem.

Thanks,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: