Yocto Project Documentation
 help / color / mirror / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: docs@lists.yoctoproject.org
Cc: Antonin Godard <antonin.godard@bootlin.com>,
	Mathieu Othacehe <othacehe@gnu.org>
Subject: [PATCH v3 1/2] profile-manual: Document the PACKAGE_KEEP_DEBUG_FRAME variable.
Date: Tue, 11 Feb 2025 17:12:38 +0100	[thread overview]
Message-ID: <20250211161239.5396-2-othacehe@gnu.org> (raw)
In-Reply-To: <20250211161239.5396-1-othacehe@gnu.org>

Document the 'PACKAGE_KEEP_DEBUG_FRAME' variable that can be used to keep the
.debug_frame ELF section when stripping.

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/ref-manual/variables.rst | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 47d4e814f..f5bd7b353 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -6243,6 +6243,15 @@ 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_DEBUG_FRAME`
+      Keep the ``.debug_frame`` ELF section when stripping during package
+      creation. You can set this variable in your ``local.conf`` file::
+
+        PACKAGE_KEEP_DEBUG_FRAME = "1"
+
+      That 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
-- 
2.47.1



  reply	other threads:[~2025-02-11 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 16:12 [PATCH v3 0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable Mathieu Othacehe
2025-02-11 16:12 ` Mathieu Othacehe [this message]
2025-02-11 16:12 ` [PATCH v3 2/2] dev-manual/debugging: Add a "Backtraces or target" section Mathieu Othacehe
2025-02-17  9:00 ` [PATCH v3 0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable Antonin Godard
2025-02-17 10:12   ` Mathieu Othacehe
2025-02-17 14:47     ` [docs] " Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250211161239.5396-2-othacehe@gnu.org \
    --to=othacehe@gnu.org \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox