[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 92071] Reading debugging info uses too much memory
From:       philippe.waroquiers () eurocontrol ! int
Date:       2005-10-05 20:36:53
Message-ID: 20051005203653.11379.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=92071         




------- Additional Comments From philippe.waroquiers eurocontrol int  2005-10-05 22:36 -------
We have downloaded valgrind from svn, compiled it.
With this last version, valgrind can properly load the debug info 
of a big executable (55 Mb of text).

A few side notes: 
* I am not sure, but it looks to me that I have
now some errors reported by valgrind that looks like false positive, when
writing to a piece of shared memory.
* I have started to run all tests, but the tests did not reach the
end (disk full). I will relaunch these now, but I have the impression
that the new valgrind can run more tests (previous version was reporting:
"not enough memory, use another tool" earlier, I think).
But it takes an very big time to run all our tests (it took 24 hours of cpu
time on a 3.7 Ghz cpu to have the disk full :).

So, in summary:
* the new address space manager is solving the debug info problem
* maybe some new (false positive) errors in the area of shared memory
* maybe new valgrind can run more tests (i.e. needs less memory).

Whenever I have more definitive answers for the last 2 "maybe", I will
get back to you.

Thanks for the nice work ...
[prev in list] [next in list] [prev in thread] [next in thread]