From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/7] elfutils: upgrade 0.196 -> 0.197
Date: Tue, 20 Oct 2026 16:13:05 +0200 [thread overview]
Message-ID: <DM9Q75SEZA82.3LDAH4WKTQUCF@bootlin.com> (raw)
In-Reply-To: <20261020092931.4330-2-jaipaul.cheernam@est.tech>
On Tue Oct 20, 2026 at 11:29 AM CEST, Jaipaul Cheernam wrote:
> Version 0.197 "Anti-Corruption"
>
> THREAD-SAFETY: New document describing the thread safety model for elfutils
> libraries when built with --enable-thread-safety. Thread
> safety support remains experimental.
>
> backends: Add unwinding support for alpha core files and processes.
>
> libdebuginfod: The progress callback function is now also invoked when
> waiting for a server's initial response.
>
> libdw: dwarf_begin_elf_type is now exported from libdw.so. Previously
> this function was missing from the exported symbols.
>
> libelf: Improved handling of corrupt ZSTD compression headers.
>
> readelf: Improved handling of corrupt .gdb_index and .debug_cu_index
> sections.
>
> translations: New Swedish translation.
>
> unstrip: Improved handling of corrupt symbol tables. When -m is given,
> the -d output path is now built from the module basename to avoid
> writing the reconstructed module image outside the intended
> output directory.
>
> - Drop already upstreamed patches
> srcfiles.patch, 0001-backends-use-sys-uio.h-instead-of-linux-uio.h-for-s.patch
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
Hi Jaipaul,
Thanks for the upgrade.
It look like the associated ptests are failing:
AssertionError:
Failed ptests:
{'elfutils': 'START: ptest-runner\n'
...
'===============================================================\n'
'2 of 258 tests did not behave as expected (2 unexpected passes)\n'
'(46 tests were not run)\n'
'Please report to https://sourceware.org/bugzilla\n'
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4777
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1409
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1398
The log in there is really verbose. I hope you can extract some useful
data from these few thousand lines of ptest log.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-10-20 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:29 [PATCH 0/7] Upgrades on 20th October Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 1/7] elfutils: upgrade 0.196 -> 0.197 Jaipaul Cheernam
2026-10-20 14:13 ` Mathieu Dubois-Briand [this message]
2026-10-20 15:33 ` [OE-core] " Jaipaul Cheernam
2026-10-20 15:42 ` Khem Raj
2026-10-20 15:31 ` [PATCH v2] " Jaipaul Cheernam
2026-10-20 17:26 ` [PATCH v3] " Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 2/7] ethtool: upgrade 7.1 -> 7.2 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 3/7] repo: upgrade 2.68.1 -> 2.69 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 4/7] libzip: upgrade 1.12 -> 1.12.1 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 5/7] libunistring: upgrade 1.4.2 -> 1.5 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 6/7] log4cplus: upgrade 2.2.0.1 -> 2.2.1 Jaipaul Cheernam
2026-10-20 9:29 ` [PATCH 7/7] python3-jsonpointer: upgrade 3.2.1 -> 3.4 Jaipaul Cheernam
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=DM9Q75SEZA82.3LDAH4WKTQUCF@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=jaipaul.cheernam@est.tech \
--cc=openembedded-core@lists.openembedded.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.