diff options
author | Alan Modra <amodra@gmail.com> | 2023-06-07 14:16:06 +0930 |
---|---|---|
committer | Alan Modra <amodra@gmail.com> | 2023-06-07 14:16:06 +0930 |
commit | ba75d1c55cb42114e3bb5c8abe37e5c2bd657a02 (patch) | |
tree | 7e5342433baeaf8305f7a9b08ab58cfc521b4dd4 /bfd/elf64-ppc.c | |
parent | 0a22a8f27df7d092620dfa1f0135a2dd7b44528a (diff) | |
download | gdb-ba75d1c55cb42114e3bb5c8abe37e5c2bd657a02.zip gdb-ba75d1c55cb42114e3bb5c8abe37e5c2bd657a02.tar.gz gdb-ba75d1c55cb42114e3bb5c8abe37e5c2bd657a02.tar.bz2 |
_bfd_free_cached_info
doc/bfdint.texi and comments in the aout and som code about this
function are just wrong, and its name is not very apt. Better would
be _bfd_mostly_destroy, and we certainly should not be saying anything
about the possibility of later recreating anything lost by this
function. What's more, if _bfd_free_cached_info is called when
creating an archive map to reduce memory usage by throwing away
symbols, the target _close_and_cleanup function won't have access to
tdata or section bfd_user_data to tidy memory. This means most of the
target _close_and_cleanup function won't do anything, and therefore
sometimes will result in memory leaks.
This patch fixes the documentation problems and moves most of the
target _close_and_cleanup code to target _bfd_free_cached_info.
Another notable change is that bfd_generic_bfd_free_cached_info is now
defined as _bfd_free_cached_info rather than _bfd_bool_bfd_true,
ie. the default now frees objalloc memory.
Diffstat (limited to 'bfd/elf64-ppc.c')
-rw-r--r-- | bfd/elf64-ppc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bfd/elf64-ppc.c b/bfd/elf64-ppc.c index a977bec..9c0762a 100644 --- a/bfd/elf64-ppc.c +++ b/bfd/elf64-ppc.c @@ -18406,7 +18406,7 @@ ppc64_elf_free_cached_info (bfd *abfd) if (opd->reloc_count == 0) free (ppc64_elf_section_data (opd)->u.opd.u.contents); - return _bfd_free_cached_info (abfd); + return _bfd_generic_bfd_free_cached_info (abfd); } #include "elf64-target.h" |