I think I might have had similar callgrind error before with older version too, can't remember correctly, though I now get the following error: checking for valgrind version... Executable range 0xb0000000-0xb082e930 is outside the acceptable range 0x80dd000-0xafcae000 valgrind: failed to load /usr/lib/valgrind/stage2: Cannot allocate memory configure: error: Unsupported version. This tool is for Valgrind 3.0.x !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/callgrind-0.10.0/work/callgrind-0.10.0/config.log !!! ERROR: dev-util/callgrind-0.10.0 failed. !!! Function econf, Line 495, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1.compile callgrind-0.10.0 2. 3. Actual Results: compile error Expected Results: compiled
What version of valgrind do you have installed?
Calculating dependencies ...done! [ebuild R ] dev-util/valgrind-3.0.1
I had this problem... it turned out that valgrind (at least from version 3, not sure about earlier versions) is incompatible with the 1GB low memory kernel patch that is widely available these days. Are you running that patch? The big thing to check is whether valgrind actually works (with 'valgrind --version') - it appears that the callgrind configure script gives the "incompatible version" error for any return from valgrind that it doesn't understand. The "Executable range 0xb0000000-0xb082e930 is outside the acceptable range 0x80dd000-0xafcae000" error comes from valgrind itself, not from the callgrind configure script.
I sure am running that patch: wakko@lapwakko ~ $ valgrind --version Executable range 0xb0000000-0xb082e930 is outside the acceptable range 0x80dd000-0xaf9c3000 valgrind: failed to load /usr/lib/valgrind/stage2: Cannot allocate memory so, is this posted as a valgrind bug then? should be fixed pronto!
I think this is fixed with callgrind-0.10.1.
I'm PRETTY sure I'm trying to compile the newest version of callgrind. It's valgrind that doesn't work for me, and callgrind doesn't compile(configure) because of it.
Can you verify the versions? The latest of both are ~x86.
I don't have access to that computer, but I've always ran ~x86. And the version number looks familiar too me. I will check this later tonight, but I'm 99% sure.
yup, it's still there...
>>> Original instance of package unmerged safely. >>> Regenerating /etc/ld.so.cache... >>> dev-util/valgrind-3.1.0 merged. >>> No packages selected for removal by clean. >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. lapwakko ~ # valgrind Killed Here I just compiled valgrind, and typing valgrind just gets me "killed"...
Any news on this? $ strace valgrind execve("/usr/bin/valgrind", ["valgrind"], [/* 71 vars */]) = 0 uname({sys="Linux", node="helios", ...}) = 0 brk(0) = 0x804d000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=172550, ...}) = 0 mmap2(NULL, 172550, PROT_READ, MAP_PRIVATE, 3, 0) = 0xa7f12000 close(3) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20P\1\000"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1202712, ...}) = 0 mmap2(NULL, 1146076, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xa7dfa000 madvise(0xa7dfa000, 1146076, MADV_SEQUENTIAL|0x1) = 0 mmap2(0xa7f0c000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x111) = 0xa7f0c000 mmap2(0xa7f10000, 7388, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xa7f10000 close(3) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa7df9000 mprotect(0xa7f0c000, 4096, PROT_READ) = 0 mprotect(0xa7f52000, 4096, PROT_READ) = 0 set_thread_area({entry_number:-1 -> 6, base_addr:0xa7df9a90, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0xa7f12000, 172550) = 0 open("/dev/urandom", O_RDONLY) = 3 read(3, "\264*\226\331", 4) = 4 close(3) = 0 readlink("/proc/self/exe", "/usr/bin/valgrind", 4096) = 17 brk(0) = 0x804d000 brk(0x806e000) = 0x806e000 execve("/usr/lib/valgrind/x86-linux/memcheck", ["valgrind"], [/* 72 vars */]) = 0 +++ killed by SIGKILL +++ Process 10036 detached So, the problem is the memcheck executable.
ok, that's progress, good work :)
Looks like a duplicate to me. Please reopen if it's not. *** This bug has been marked as a duplicate of 128684 ***
