[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:       Tom Hughes <tom () compton ! nu>
Date:       2005-08-26 14:47:17
Message-ID: 20050826144717.7204.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 tom compton nu  2005-08-26 16:47 -------
Because you've effectively got two programs (valgrind and the client) running as part \
of a single process you have to be very careful.

Originally there was only one libc so valgrind couldn't use it as it might conflict \
with the client. The current implementation means that two copies of libc are loaded, \
one for valgrind and one for the client, but as they will both ask the kernel to do \
things on behalf of the process there is still a need to be careful and it is better \
if valgrind relies on nothing and does everything itself so we know exactly what is \
happening and can avoid any sort of conflict with the client program.


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