On Fri, Jun 19, 2026 at 12:15:32AM +0000, [email protected] wrote:
> A new failure has been detected on builder elfutils-debian-armhf while
> building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/6/builds/521
>
> Build state: failed test (failure)
> Revision: 0e8b57aa36d80fd8e366c6e22f5bc96fdfe7c062
> Worker: debian-armhf
> Build Reason: (unknown)
> Blamelist: Mark Wielaard <[email protected]>
> [...]
> - 7: make check ( failure )
> Logs:
> - stdio:
> https://builder.sourceware.org/buildbot/#/builders/6/builds/521/steps/7/logs/stdio
> - test-suite.log:
> https://builder.sourceware.org/buildbot/#/builders/6/builds/521/steps/7/logs/test-suite_log
I wish I understood this issue better:
TID 11656:
# 0 0xa64899cc __clone
/srv/builder/worker/elfutils-debian-armhf/build/tests/backtrace:
dwfl_thread_getframes: no matching address range
/srv/builder/worker/elfutils-debian-armhf/build/tests/backtrace:
dwfl_thread_getframes: no matching address range
backtrace: backtrace.c:81: callback_verify: Assertion `seen_main' failed.
We see it across different arches. It looks like we sometimes
"interrupt" the clone call on the wrong instruction and then fail to
produce a backtrace for the main thread. But it never happens when
trying to replicate by hand :{ It looks like a unfortunate
signal/scheduling issue.
Cheers,
Mark
