The --no_eager_load_debug option causes the
linker to remove debug section data from memory after object loading.
This lowers the peak memory usage of the linker at the expense of
some linker performance, because much of the debug data has to be
loaded again when the final image is written.
Using --no_eager_load_debug option does not
affect the debug data that is written into the ELF file.
The default is --eager_load_debug.
Note
The resulting image or object built without debug information
might differ by a small number of bytes. This is because the .comment section
contains the linker command line used, where the options have differed
from the default (the default is --eager_debug_load).
Therefore --no_eager_load_debug images are a little
larger and contain Program Header and possibly a Section Header
a small number of bytes later. Use --no_comment_section to
eliminate this difference.
This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.
ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.