All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <raj.khem@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Khem Raj" <khem.raj@oss.qualcomm.com>
Subject: Re: [OE-core] [PATCH] elfutils: Fix backtrace ptests on musl
Date: Sat, 24 Oct 2026 19:31:18 +0200	[thread overview]
Message-ID: <DMD8X3RTVWMC.Z82034UND8KZ@bootlin.com> (raw)
In-Reply-To: <20261022154937.1328672-1-khem.raj@oss.qualcomm.com>

On Thu Oct 22, 2026 at 5:49 PM CEST, Khem Raj via lists.openembedded.org wrote:
> musl is built with -fno-asynchronous-unwind-tables, so libc.so carries
> almost no .eh_frame and its CFI only lives in .debug_frame. Without it the
> unwinder cannot get out of abort () and run-backtrace-dwarf.sh fails with
> "No DWARF information found". Add musl-dbg to the ptest dependencies, like
> glibc-dbg for glibc.
>
> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
> ---

Hi Khem,

Thanks for your patch.

It looks like this is breaking some ptest on qemux86-64-musl:

AssertionError:
Failed ptests:
{'elfutils': 'START: ptest-runner\n'
...
             '===============================================================\n'
             '2 of 259 tests did not behave as expected (2 unexpected passes)\n'
             '(45 tests were not run)\n'
             'Please report to https://sourceware.org/bugzilla\n'
             '===============================================================\n'

https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1435

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2026-10-24 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 15:49 [PATCH] elfutils: Fix backtrace ptests on musl Khem Raj
2026-10-24 17:31 ` 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=DMD8X3RTVWMC.Z82034UND8KZ@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=khem.raj@oss.qualcomm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.