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

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



On Thu, Jan 13, 2005 at 08:45:31AM -0500, Andrés Roldán wrote:
> > 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.

This bug was reported against valgrind 1:2.2.0-4, so unless that's
inaccurate, given that no one can reproduce the error a prelink bug seems
more likely.

Cheers,
-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: