Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	 Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [OE-core] [PATCH v2] lib/oe/package: Add strip keep-section support
Date: Tue, 04 Feb 2025 15:25:26 +0100	[thread overview]
Message-ID: <87tt99g52h.fsf@gnu.org> (raw)
In-Reply-To: <CANNYZj9tjKN_Evr3KR7mNDMABXAgbLoCFL=EnoQviXa4+Mg7Kw@mail.gmail.com> (Alexander Kanavin's message of "Tue, 4 Feb 2025 13:50:02 +0100")


> Thanks. But you still need to look at existing minidebuginfo tests and
> see if you can enhance them. Otherwise we have a variable that isn't
> tested.

OK, I will check want I can do.

> Also, if minidebuginfo distro feature is enabled, do we actually need
> this level of control? Why not just always have the needed bits?

On some architectures, such as x86_64 and aarch64, the .eh_frame section
that is *not* stripped because used for C++ exception handling, can be
used for DWARF-based stack unwinding purposes.

On those architectures, one can rely on .eh_frame + minidebuginfo to get
DWARF based backtraces. So no need for the PACKAGE_KEEP_SECTIONS there.

However, on ARMv7, the .eh_frame section is empty and the ARM specific .exidx
section is not enough to get full backtraces, as discussed here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117941

For that specific architecture, it then makes sense to instruct 'strip'
to leave the .debug_frame section. By setting for instance:

PACKAGE_KEEP_SECTIONS:armv7a = ".debug_frame"

So minidebuginfo and PACKAGE_KEEP_SECTIONS are two very different
things, serving different purposes. Even though the combination of both
is required on some architectures to get full backtraces, I don't think
that they should be tied together.

> You can split into at least four commits:
>
> - change of runstrip signature
> - change of strip_execs signature
> - adding new variable to package.py
> - adding new variable to staging class.

OK, thanks for the suggestion.

Mathieu


  reply	other threads:[~2025-02-04 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 10:37 [PATCH v2] lib/oe/package: Add strip keep-section support Mathieu Othacehe
2025-02-04 11:37 ` [OE-core] " Alexander Kanavin
2025-02-04 11:39   ` Alexander Kanavin
2025-02-04 12:36   ` Mathieu Othacehe
2025-02-04 12:50     ` Alexander Kanavin
2025-02-04 14:25       ` Mathieu Othacehe [this message]
2025-02-04 19:02         ` Alexander Kanavin
2025-02-27 15:28 ` Richard Purdie
2025-02-28  9:09   ` Mathieu Othacehe
2025-02-28 10:37     ` Richard Purdie
2025-03-01  9:31       ` Mathieu Othacehe
2025-03-01  9:57         ` Richard Purdie
2025-03-06  7:34           ` Mathieu Othacehe
2025-03-01 16:11         ` Khem Raj

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=87tt99g52h.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=quentin.schulz@cherry.de \
    /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