On May 12 12:37, Ryan Johnson wrote: > On 11/05/2011 3:31 PM, Corinna Vinschen wrote: > >On May 11 13:46, Ryan Johnson wrote: > >>Also, the cygheap isn't a normal windows heap, is it? I thought it > >>was essentially a statically-allocated array (.cygheap) that gets > >>managed as a heap. I guess since it's part of cygwin1.dll we already > >>do sort of report it... > >The cygheap is the last section in the DLL and gets allocated by the > >Windows loader. The memory management is entirely in Cygwin (cygheap.cc). > >Cygwin can raise the size of the cygheap, but only if the blocks right > >after the existing cygheap are not already allocated. > Would it make sense to give that section, and the one(s) which > immediately follow it, the tag "[cygheap]" rather than > "/usr/bin/cygwin1.dll" and nothing? It would require struct pefile > to identify the section, plus some trickery in format_process_maps > to treat the cygwin dll and adjacent succeeding allocation(s) > specially.
I wouldn't do that. Just because there's a allocated block right after the cygheap doesn't mean it's part of the cygheap. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
