This is the mail archive of the
cygwin-patches
mailing list for the Cygwin project.
Re: Rewrite/fix cygwin1.dbg generation
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-patches at cygwin dot com
- Date: Sat, 3 Nov 2007 22:20:28 -0400
- Subject: Re: Rewrite/fix cygwin1.dbg generation
- References: <472CB021.5040806@portugalmail.pt> <472CB37A.407FAE34@dessent.net>
- Reply-to: cygwin-patches at cygwin dot com
On Sat, Nov 03, 2007 at 10:44:26AM -0700, Brian Dessent wrote:
>Pedro Alves wrote:
>
>> The dllfixdbg hunk looks hard to read. Here's what is looks
>> like after patching:
>
>I think that if whatever bugs used to exist in older binutils PE support
>that necessitated this hackery are now gone, we can just do away with
>dllfixdbg alltogether and just put this:
>
>> ${STRIP} --strip-debug ${DLL} -o stripped-${DLL}
>> ${STRIP} --only-keep-debug ${DLL} -o ${DBG}
>> ${OBJCOPY} --add-gnu-debuglink=${DBG} stripped-${DLL} ${DLL}
>> rm -f stripped-${DLL}
>
>...in the Makefile.
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?
cgf