Summary: | callgrind-0.10.1-r1 emerge fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vasilis Lourdas <bugs> |
Component: | Current packages | Assignee: | Caleb Tennis (RETIRED) <caleb> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | fischer |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | config.log |
Description
Vasilis Lourdas
2006-04-30 03:57:28 UTC
Forgot to mention that I have valgrind-3.1.1 installed. (In reply to comment #0) > checking for valgrind version... > configure: error: Unsupported version. This tool is for Valgrind 3.0.x/3.1.x > > !!! Please attach the following file when filing a report to bugs.gentoo.org: > !!! /var/tmp/portage/callgrind-0.10.1-r1/work/callgrind-0.10.1/config.log Please provide config.log. Created attachment 85857 [details]
config.log
The config.log file.
(In reply to comment #3) > Created an attachment (id=85857) [edit] > config.log As far as I understand, the configure script cannot determine Valgrind's version (there is an empty string). Is Valgrind correctly installed? Have you tried to run it? What is the output from valgrind --version ? $ valgrind --version Killed $ It segfaults. Maybe it's related to bug http://bugs.gentoo.org/show_bug.cgi?id=110007 and the 1GB low memory kernel patch that was included by default with kernel 2.6.16 (I think). (In reply to comment #5) > $ valgrind --version > Killed > $ > > It segfaults. Maybe it's related to bug > http://bugs.gentoo.org/show_bug.cgi?id=110007 and the 1GB low memory kernel > patch that was included by default with kernel 2.6.16 (I think). I suggest you mark this bug as invalid (is not a callgrind bug) and try to dig into the segfault problem. Try compiling valgrind with debug flags and run it in a debugger. Try out ltrace and strace. If it is a valgrind specific bug, report it upstream. (In reply to comment #6) > I suggest you mark this bug as invalid (is not a callgrind bug) and try to dig > into the segfault problem. Try compiling valgrind with debug flags and run it > in a debugger. Try out ltrace and strace. If it is a valgrind specific bug, > report it upstream. OK, I will follow your suggestions. |