Your message dated Tue, 17 Jun 2008 09:27:07 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Closing bug
has caused the Debian Bug report #319243,
regarding Does not start (failed to load /usr/lib/valgrind/stage2: Cannot
allocate memory)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
319243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319243
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: valgrind
Version: 1:2.4.0-3
Severity: important
Hello,
Starting valgrind prints:
Executable range 0xb0000000-0xb0200de0 is outside the
acceptable range 0x80d3000-0xaff8d000
valgrind: failed to load /usr/lib/valgrind/stage2: Cannot allocate memory
I had this problem before, I think it's because of my kernel (ck patchset
with 1GB low mem enabled). It was fixed for a while, but appeared again some
time ago.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-ck2
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages valgrind depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
Versions of packages valgrind recommends:
ii gdb 6.3-6 The GNU Debugger
-- no debconf information
--
If you can count your money, you don't have a billion dollars.
-- J. Paul Getty
--- End Message ---
--- Begin Message ---
Bug is not longer present on current version
--- End Message ---
