[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/5522] New: Section contents partially overwritten with zero

From: SebastianR at gmx dot de
Subject: [Bug ld/5522] New: Section contents partially overwritten with zero
Date: 25 Dec 2007 00:38:04 -0000


When linking the attached files using the command line

  ld -q -T bss.lds attention.o libbss.a -o attention.bso

with ld 2.18 targeted for ELF (tested on Linux with version 2.18-1 from Debian,
and on Windows by building binutils 2.18.50 on MinGW with target "i386-pc-elf"),
the first 8 bytes of the section ".bs.server.name" are overwritten with zero. 

  objdump -s -j .bs.server.name attention.o


  Contents of section .bs.server.name:
   0000 41747465 6e74696f 6e536967 6e00      AttentionSign.


  objdump -s -j .bs.server.name attention.bso


  Contents of section .bs.server.name:
   400620 00000000 00000000 6e536967 6e00      ........nSign.

A similar problem occurs with the file "car.o"; in that case the entire contents
of ".bs.server.name" and ".bs.server.service" come out as zero. The section
lengths are correct, however.

Many similar files are linked just fine, but the problem is reproducable with
these specific files, even though it looks pretty random to me. There are no
relocs in the affected sections, so the section contents should stay exactly the
same IMHO.

Please mail me if you want to generate the files yourself.

Sebastian Reichelt

           Summary: Section contents partially overwritten with zero
           Product: binutils
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: SebastianR at gmx dot de
                CC: bug-binutils at gnu dot org
 GCC build triplet: same as host
  GCC host triplet: i386-linux-elf (also tested with MinGW)
GCC target triplet: i386-linux-elf and i386-pc-elf


------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]