Remove FIXME in solib-aix.c:solib_aix_relocate_section_addresses

This issue should now be fixed thanks to a change in bfd removing
the SEC_ALLOC flag from all sections that do not get mapped to
memory.

gdb/ChangeLog:

        * solib-aix.c (solib_aix_relocate_section_addresses):
        Remove FIXME comment.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 9f7b97228da91561c409f2135f1879db30a536cb..f7b27f58b446f97188d7ff415ff884249b5aa68d 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -4,6 +4,11 @@
        For the .bss section action, apply the same offset as
        the .data section.
 
+2013-05-10  Joel Brobecker  <brobecker@adacore.com>
+
+       * solib-aix.c (solib_aix_relocate_section_addresses):
+       Remove FIXME comment.
+
 2013-05-10  Joel Brobecker  <brobecker@adacore.com>
 
        PR tdep/15420:

diff --git a/gdb/solib-aix.c b/gdb/solib-aix.c
index 4672b588ce34c0186c16ba3df459f540fb574d3b..5d15e7045af3041dc3a3b305f7793a7f9b50c850 100644 (file)
--- a/gdb/solib-aix.c
+++ b/gdb/solib-aix.c
@@ -432,16 +432,6 @@ solib_aix_relocate_section_addresses (struct so_list *so,
   else
     {
       /* All other sections should not be relocated.  */
-      /* FIXME: GDB complains that the .loader section sometimes
-        overlaps with other sections (Eg: the .data section).
-        As far as I can tell, the loader section had the LOAD flag
-        set, but not the RELOC.  So it should not be relocated.
-        There seems to be a problem there, and maybe it has to do
-        with setting sec->addr to 0 (when the vma is indeed 0).
-        But even if there wasn't, the problem then becomes the fact
-        that many shared objects inside shared libraries have
-        a .loader section whose vma is 0, thus also triggering
-        an overlap warning.  */
       sec->addr = bfd_section_vma (abfd, bfd_sect);
       sec->endaddr = sec->addr + bfd_section_size (abfd, bfd_sect);
     }