Mail Archives: cygwin/2005/06/08/17:44:09
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/
- Raw text -