* [PATCH] profile-manual: Document the PACKAGE_KEEP_SECTIONS variable.
@ 2025-02-04 10:28 Mathieu Othacehe
2025-02-04 14:32 ` [docs] " Antonin Godard
0 siblings, 1 reply; 3+ messages in thread
From: Mathieu Othacehe @ 2025-02-04 10:28 UTC (permalink / raw)
To: docs; +Cc: Mathieu Othacehe
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 ++++++
1 file changed, 6 insertions(+)
diff --git a/documentation/profile-manual/intro.rst b/documentation/profile-manual/intro.rst
index 317912552..a7243c1ca 100644
--- a/documentation/profile-manual/intro.rst
+++ b/documentation/profile-manual/intro.rst
@@ -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"
--
2.47.1
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [docs] [PATCH] profile-manual: Document the PACKAGE_KEEP_SECTIONS variable.
2025-02-04 10:28 [PATCH] profile-manual: Document the PACKAGE_KEEP_SECTIONS variable Mathieu Othacehe
@ 2025-02-04 14:32 ` Antonin Godard
2025-02-05 15:55 ` Mathieu Othacehe
0 siblings, 1 reply; 3+ messages in thread
From: Antonin Godard @ 2025-02-04 14:32 UTC (permalink / raw)
To: othacehe, docs
Hi Mathieu,
On Tue Feb 4, 2025 at 11:28 AM CET, Mathieu Othacehe via lists.yoctoproject.org wrote:
> 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 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/documentation/profile-manual/intro.rst b/documentation/profile-manual/intro.rst
> index 317912552..a7243c1ca 100644
> --- a/documentation/profile-manual/intro.rst
> +++ b/documentation/profile-manual/intro.rst
> @@ -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
Thanks for this patch. But this addition produces the following error:
.../documentation/profile-manual/intro.rst:79:term not in glossary: 'PACKAGE_KEEP_SECTIONS' [ref.term]
because PACKAGE_KEEP_SECTIONS is not documented in ref-manual/variables.rst.
Hence, you cannot make a reference (with :term:) to it.
Could you add documentation for this variable there?
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-02-05 15:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-02-04 10:28 [PATCH] profile-manual: Document the PACKAGE_KEEP_SECTIONS variable Mathieu Othacehe
2025-02-04 14:32 ` [docs] " Antonin Godard
2025-02-05 15:55 ` Mathieu Othacehe
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.