bug-binutils
[Top][All Lists]
Advanced

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

[Bug ld/494] New: Problem when relocating an executable


From: Manfred dot Neugebauer at siemens dot com
Subject: [Bug ld/494] New: Problem when relocating an executable
Date: 2 Nov 2004 15:08:52 -0000

Hallo,

We use the Gnu tools to create executables for a proprietary realtime OS. The 
executables are created on Windows XP / cygwin using cross compiling and 
linking. We use the linker option --emit-relocs to be able to relocate the 
executable on our target using a special target loader).

This procedure works fine with the loader version 2.14 20030612. Now we want to 
move to the loader 2.15 and have a problem. It looks that certain variables 
(located in the .data, .rodata or .bss section) don't have an entry in 
the .reltext section, although their symbol is available. So we don't find them 
with our linker and the application crashes, since the default address 
0x804xxxx is used.

A first look into this problem showed that these data are linked into the 
executable as part of static library. It may also be related to the fact that 
this information is static to a source file. If helpful, I can provide a simple 
test program which shows this problem.

Thanks. Manfred.

-- 
           Summary: Problem when relocating an executable
           Product: binutils
           Version: 2.15
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: Manfred dot Neugebauer at siemens dot com
                CC: Manfred dot Neugebauer at siemens dot com,bug-binutils
                    at gnu dot org
 GCC build triplet: --host=i586-pc-cygwin --target=i586-rmos-elf
  GCC host triplet: cygwin
GCC target triplet: proprietary realtime OS


http://sources.redhat.com/bugzilla/show_bug.cgi?id=494

------- 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]