Rewrite/fix cygwin1.dbg generation
Mon Nov 5 08:41:00 GMT 2007
On Nov 4 04:00, Pedro Alves wrote:
> Christopher Faylor wrote:
>> If that is the case, then this is a welcome change but I'm wondering if
>> it really is true. Since the debug stripping is linked to the way that
>> cygwin manages the cygwin heap, it is possible that things only appear
>> to work until you allocate more space in the heap. Has anyone tried the
>> above with a program that, say, opens a lot of file handles?
> Ah, got it. VirtualAlloc fails on the first _csbrk, since it
> is tripping on the VMA of .gnu_debuglink ... I assumed it would
> not be a problem, since it isn't ALLOCced, but oh well...
> I tried adding an EXCLUDE/NOLOAD flag to .gnu_debuglink, but no
> can do.
That was the reason for creating the .dbg file in the first place,
wasn't it? The Windows loader appears to allocate the full size of all
sections of the image, including the NOLOAD and DEBUG sections. Sort of
counterproductive but there seem to be no way around it.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
More information about the Cygwin-patches