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 0/2] Document the PACKAGE_KEEP_DEBUG_FRAME variable
Date: Tue, 11 Feb 2025 17:12:37 +0100 [thread overview]
Message-ID: <20250211161239.5396-1-othacehe@gnu.org> (raw)
Hello,
That series is introducing a PACKAGE_KEEP_DEBUG_FRAME variable that can be
used to keep the .debug_frame ELF section when stripping packages.
It is then building upon that to present how to get human-readable backtraces
on target, possibly also relying on the minidebuginfo mechanism.
Thanks,
Mathieu
v2: https://lists.yoctoproject.org/g/docs/message/6252
poky: https://git.yoctoproject.org/poky/commit/?h=master-next&id=10448200b63bdc45b39504ebcddd85b5f274f0c4
Changelog:
v2: Fix a build issue
v3: Document the PACKAGE_KEEP_DEBUG_FRAME
variable rather that the PACKAGE_KEEP_SECTIONS variable because the former
approach was preferred and merged into poky.
Mathieu Othacehe (2):
profile-manual: Document the PACKAGE_KEEP_DEBUG_FRAME variable.
dev-manual/debugging: Add a "Backtraces or target" section
documentation/dev-manual/debugging.rst | 55 ++++++++++++++++++++++++++
documentation/ref-manual/variables.rst | 9 +++++
2 files changed, 64 insertions(+)
--
2.47.1
next reply other threads:[~2025-02-11 16:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 16:12 Mathieu Othacehe [this message]
2025-02-11 16:12 ` [PATCH v3 1/2] profile-manual: Document the PACKAGE_KEEP_DEBUG_FRAME variable Mathieu Othacehe
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-1-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 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.