Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 8 Jun 2005 17:43:42 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Problem with using stripped cygwin1.dll built from CVS Message-ID: <20050608214341.GA21349@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <42A6298E DOT 303 AT acm DOT org> <42A62DAE DOT F4153556 AT dessent DOT net> <42A632C5 DOT 7040306 AT acm DOT org> <20050608084920 DOT GN23172 AT calimero DOT vinschen DOT de> <20050608143656 DOT GB17698 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050608143656.GB17698@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.8i On Wed, Jun 08, 2005 at 10:36:56AM -0400, Christopher Faylor wrote: >On Wed, Jun 08, 2005 at 10:49:20AM +0200, Corinna Vinschen wrote: >>On Jun 7 16:50, David Rothenberger wrote: >>> On 6/7/2005 4:28 PM, Brian Dessent wrote: >>> >Part of the new cygheap changes that cgf recently checked in, were a >>> >number of changes/tweaks to the linker script. It's possible that your >>> >checkout happened in the middle of those changes, or you didn't get them >>> >all. Try a recent checkout. (If you are already using an up to date >>> >tree, then ignore this...) >>> >>> Total up-to-date tree. I did a cvs update -A this afternoon. I also get >>> this same error if I run strip (w/o args) on the DLL from the latest >>> snapshot. >> >>Weird. I had this when trying to build Cygwin with Dwarf2 debugging >>information and the linker script wasn't aware of the additional sections. >>Could you paste the output of `objdump -h cygwin1.dll' of a stripped and >>an unstripped DLL? > >I understand the problem. It's a binutils bug that I'm investigating. >Either gas or ld is marking NOLOAD sections as "read only" and that is >causing windows to actually load them into memory. There's a new "test" version of binutils available which seems to fix this problem. I'm awaiting approval for a patch in the binutils mailing list before making this version official. This turns out to have been a long-time bug in binutils, AFAICT. The debug sections that the GNU linker produces were not properly marked as "noload" so debug data was actually loaded into memory. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/