From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <othacehe@gnu.org>, <openembedded-core@lists.openembedded.org>
Cc: "Alexander Kanavin" <alex.kanavin@gmail.com>,
"Khem Raj" <raj.khem@gmail.com>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH 1/1] lib/oe/package: Add strip keep-section support
Date: Sat, 12 Sep 2026 14:18:27 +0200 [thread overview]
Message-ID: <DLDBYP5W0AF2.280D6PM6XUF48@bootlin.com> (raw)
In-Reply-To: <20260911220138.32414-2-othacehe@gnu.org>
On Sat Sep 12, 2026 at 12:01 AM CEST, Mathieu Othacehe via lists.openembedded.org wrote:
> On 32-bit Arm, the .ARM.extab and .ARM.exidx unwinding sections do not
> always provide enough information to get a full backtrace on C++
> exceptions:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117941
>
> In addition to those unwinding sections, GCC also emits unwinding
> instructions in DWARF format under the .debug_frame section. By
> instructing 'strip' not to remove that section, libunwind can use it
> to produce a full backtrace, for example when an unhandled C++
> exception is thrown.
>
> Add a PACKAGE_KEEP_SECTIONS variable, listing space separated ELF
> section names that should be kept around instead of stripped, for
> example:
>
> PACKAGE_KEEP_SECTIONS:pn-myrecipe = ".debug_frame"
>
> This variable is never applied to kernel modules, which are covered
> by CONFIG_UNWINDER_* instead.
>
> Add a oe-selftest case building core-image-minimal for qemuarm, and
> checking with readelf that busybox loses its .debug_frame section by
> default, but keeps it once PACKAGE_KEEP_SECTIONS is set.
>
> Signed-off-by: Mathieu Othacehe <othacehe@gnu.org>
> ---
Hi Mathieu,
Thanks for your patch.
It looks like the added test is failing on the autobuilder:
2026-09-12 09:19:34,528 - oe-selftest - INFO - package.PackageKeepSections.test_package_keep_sections (subunit.RemotedTestCase)
2026-09-12 09:19:34,529 - oe-selftest - INFO - ... ERROR
...
2026-09-12 09:19:34,529 - oe-selftest - INFO - 5: 28/54 531/772 (122.95s) (0 failed) (package.PackageKeepSections.test_package_keep_sections)
2026-09-12 09:19:34,529 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/package.py", line 248, in test_package_keep_sections
self.assertFalse(has_section(".debug_frame"),
~~~~~~~~~~~^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/package.py", line 241, in has_section
tar.extract("./usr/bin/busybox.nosuid", path=unpackedfs)
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/python3.13/tarfile.py", line 2365, in extract
tarinfo = self._get_extract_tarinfo(member, filter_function, path)
File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/python3.13/tarfile.py", line 2372, in _get_extract_tarinfo
tarinfo = self.getmember(member)
File "/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/python3.13/tarfile.py", line 2041, in getmember
raise KeyError("filename %r not found" % name)
KeyError: "filename './usr/bin/busybox.nosuid' not found"
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4649
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4842
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-09-12 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 22:01 [PATCH v3 0/1] lib/oe/package: Add strip keep-section support Mathieu Othacehe
2026-09-11 22:01 ` [PATCH 1/1] " Mathieu Othacehe
2026-09-12 12:18 ` Mathieu Dubois-Briand [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=DLDBYP5W0AF2.280D6PM6XUF48@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=othacehe@gnu.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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