[Bug ld/16910] Failed to relocate attributes of debug information when the sym is wrapped

[amodra at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=16910

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |amodra at gmail dot com
         Resolution|---                         |FIXED

--- Comment #2 from Alan Modra <amodra at gmail dot com> ---
commit b71c404358dbc78d3e84c4299c6139c5291ac441
Author: Alan Modra <address@hidden>
Date:   Tue Jun 10 23:07:52 2014 +0930

    add pr number to changelog

commit 7b8e2718e4412ddc1e42c6a68166de919eb62221
Author: Alan Modra <address@hidden>
Date:   Tue Jun 10 23:02:55 2014 +0930

    missing changelog entries for 8a5da09b9

commit 8a5da09b9e326a19e78b20a1021a5148ea0484b0
Author: Alan Modra <address@hidden>
Date:   Tue Jun 10 21:50:21 2014 +0930

    Unwrap symbols for debug information

    Fixes issues with dwz multi-file (-m) and ld's -wrap option.
    Symbols referenced from DWARF debug info in a separate file, eg. to
    specify low and high pc, must use the real symbol.  The DWARF info
    is specifying attributes of the real function, not one interposed
    with --wrap.

    include/
        * bfdlink.h (unwrap_hash_lookup): Declare.
    bfd/
        * linker.c (unwrap_hash_lookup): New function.
        * elf-bfd (RELOC_FOR_GLOBAL_SYMBOL): Call unwrap_hash_lookup.
        * elf32-i370.c (i370_elf_relocate_section): Likewise.
        * elf32-m32c.c (m32c_elf_relocate_section): Likewise.
        * elf32-m32r.c (m32r_elf_relocate_section): Likewise.
        * elf32-score.c (s3_bfd_score_elf_relocate_section): Likewise.
        * elf32-score7.c (s7_bfd_score_elf_relocate_section): Likewise.
        * elf32-spu.c (spu_elf_relocate_section): Likewise.
        * elf64-hppa.c (elf64_hppa_relocate_section): Likewise.

-- 
You are receiving this mail because:
You are on the CC list for the bug.