@@ -75,3 +75,9 @@ Additionally, in order to generate the right type of debug info, we also need to
set :term:`PACKAGE_DEBUG_SPLIT_STYLE` in the ``local.conf`` file::
PACKAGE_DEBUG_SPLIT_STYLE = 'debug-file-directory'
+
+When you are building a stripped image, you can also keep some specific ELF
+sections in the image by setting :term:`PACKAGE_KEEP_SECTIONS` in the
+``local.conf`` file::
+
+ PACKAGE_KEEP_SECTIONS = ".debug_frame"
@@ -6243,6 +6243,18 @@ system and gives an overview of their function and contents.
install, the build system does not generate an error. This variable
is generally not user-defined.
+ :term:`PACKAGE_KEEP_SECTIONS`
+ Specifies a list of ELF sections that should be kept when stripping
+ during package creation. You can set this variable in your
+ ``local.conf`` file.
+
+ For example, the following::
+
+ PACKAGE_KEEP_SECTIONS = ".debug_frame"
+
+ will result in passing the ``--keep-section=.debug_frame`` argument to
+ the ``strip`` command.
+
:term:`PACKAGE_PREPROCESS_FUNCS`
Specifies a list of functions run to pre-process the
:term:`PKGD` directory prior to splitting the files out
Document the 'PACKAGE_KEEP_SECTIONS' variable that can be used to keep some specific ELF sections while stripping binaries and libraries. That one can then be used to keep the .debug_frame section around for example, this way: PACKAGE_KEEP_SECTIONS = ".debug_frame" By using libunwind + minidebuginfo, that provides a way for users to get debug_frame based backtraces on target. Signed-off-by: Mathieu Othacehe <othacehe@gnu.org> --- documentation/profile-manual/intro.rst | 6 ++++++ documentation/ref-manual/variables.rst | 12 ++++++++++++ 2 files changed, 18 insertions(+)