From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: ecordonnier@snap.com
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] manuals: document minidebuginfo
Date: Thu, 07 Dec 2023 14:54:47 +0100 [thread overview]
Message-ID: <6rzfymun9q.fsf@pengutronix.de> (raw)
In-Reply-To: <20231207134322.3185149-1-ecordonnier@snap.com>
Hi Etienne,
thanks for your documentation of minidebuginfo!
On Thu, Dec 07 2023 at 14:43 +0100, "Etienne Cordonnier via lists.yoctoproject.org" <ecordonnier=snap.com@lists.yoctoproject.org> wrote:
> From: Etienne Cordonnier <ecordonnier@snap.com>
>
> Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
> ---
> documentation/dev-manual/debugging.rst | 15 +++++++++++++++
> documentation/ref-manual/features.rst | 3 +++
> 2 files changed, 18 insertions(+)
>
> diff --git a/documentation/dev-manual/debugging.rst b/documentation/dev-manual/debugging.rst
> index fea2cb30a..75dc53649 100644
> --- a/documentation/dev-manual/debugging.rst
> +++ b/documentation/dev-manual/debugging.rst
> @@ -1173,6 +1173,21 @@ To support this kind of debugging, you need do the following:
> Consider that this will reduce the application's performance and is
> recommended only for debugging purposes.
>
> +Enabling Minidebuginfo
> +======================
> +
> +Enabling the DISTRO_FEATURES minidebuginfo adds a compressed ELF section ".gnu_debugdata"
> +to all binary files, containing only function names, and thus increasing the size of the
> +binaries only of 5 to 10%. For comparison, full debug symbols can be 10 times as big as
s/of 5 to 10%/by 5 to 10%/
Best regards
Ulrich
> +a stripped binary, and it is thus not always possible to deploy full debug symbols.
> +Minidebuginfo data allows, on the one side, to retrieve a call-stack using
> +gdb (command backtrace) without deploying full debug-symbols to the target. It also
> +allows to retrieve a symbolicated call-stack when using systemd-coredump to manage
> +coredumps (commands "coredumpctl list" and "coredumpctl info").
> +
> +This feature was created by Fedora, see https://fedoraproject.org/wiki/Features/MiniDebugInfo for
> +more details.
> +
> Other Debugging Tips
> ====================
>
> diff --git a/documentation/ref-manual/features.rst b/documentation/ref-manual/features.rst
> index dd14339bc..1320c3a58 100644
> --- a/documentation/ref-manual/features.rst
> +++ b/documentation/ref-manual/features.rst
> @@ -161,6 +161,9 @@ metadata, as extra layers can define their own:
> - *keyboard:* Include keyboard support (e.g. keymaps will be loaded
> during boot).
>
> +- *minidebuginfo:* Add minimal debug symbols :ref:`(minidebuginfo)<dev-manual/debugging:enabling minidebuginfo>`
> + to binary files containing, allowing coredumpctl and gdb to show symbolicated stack traces.
> +
> - *multiarch:* Enable building applications with multiple architecture
> support.
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-12-07 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 13:43 [PATCH] manuals: document minidebuginfo ecordonnier
2023-12-07 13:54 ` Ulrich Ölmann [this message]
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=6rzfymun9q.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=docs@lists.yoctoproject.org \
--cc=ecordonnier@snap.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).