[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-08-26 14:24:22
Message-ID: 20050826142422.760.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-08-26 16:24 -------
> Using malloc is not a solution because it allows the mapping to be in the 
> client address space which breaks the separation of client data and valgrind
>  data. It also introduces a libc dependency and we're trying to get rid of 
> those.

I imagine that when valgrind is busy reading symbol tables, that the
client is "blocked/idle/stopped".

So, the malloc could be replaced by:
  use brk and sbrk to extend the memory available at the end of the heap
  read the file in this memory.
  process the symbol table
  reduce the memory by calling brk/sbrk again

As I imagine that the client is not doing anything during that time,
the client cannot corrupt valgrind memory.

Disclaimer: as I do not know the real reason to separate valgrind data
from client data, and to avoid dependencies to glibc, and as I do know
almost nothing about valgrind implementation, the above is very probably
stupid, but I will surely learn something from your reply :).
[prev in list] [next in list] [prev in thread] [next in thread]