Hi,
On Tue, Apr 13, 2021 at 04:54:13PM +0000, [email protected] wrote:
> The Buildbot has detected a failed build on builder whole buildset while
> building elfutils.
> Full details are available at:
> https://builder.wildebeest.org/buildbot/#builders/11/builds/702
>
> Buildbot URL: https://builder.wildebeest.org/buildbot/
>
> Worker for this Build: fedora-ppc64le
This was a different issue:
FAIL: run-backtrace-native-core.sh
==================================
/usr/bin/coredumpctl
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.
PID: 10643 (backtrace-child)
UID: 1002 (mjw)
GID: 1002 (mjw)
Signal: 6 (ABRT)
Timestamp: Tue 2021-04-13 12:59:04 UTC (2s ago)
Command Line:
/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace-child
--gencore
Executable:
/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace-child
Control Group: /user.slice/user-1002.slice/session-2.scope
Unit: session-2.scope
Slice: user-1002.slice
Session: 2
Owner UID: 1002 (mjw)
Boot ID: 4684256e966845baad90ffbef2d3c976
Machine ID: fa20d94f66194772a93b94464bd75866
Hostname: rh-power-vm60.fit.vutbr.cz
Storage:
/var/lib/systemd/coredump/core.backtrace-child.1002.4684256e966845baad90ffbef2d3c976.10643.1618318744000000.lz4
Message: Process 10643 (backtrace-child) of user 1002 dumped core.
Stack trace of thread 10644:
#0 0x00007fffadc28d48 raise (libpthread.so.0)
#1 0x000000012d5e14a4 n/a
(/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace-child)
#2 0x000000012d5e15cc n/a
(/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace-child)
#3 0x000000012d5e161c n/a
(/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace-child)
#4 0x000000012d5e1648 n/a
(/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace-child)
#5 0x00007fffadc18c10 start_thread (libpthread.so.0)
#6 0x00007fffadb2d8a8 __clone (libc.so.6)
0x7fffae620000 0x7fffae630000 linux-vdso64.so.1
0x7fffae640000 0x7fffae681108 ld64.so.2
0x7fffad590000 0x7fffad5c0428 libgcc_s.so.1
0x7fffad5d0000 0x7fffad6f0128 libm.so.6
0x7fffad700000 0x7fffad9955f8 libstdc++.so.6
0x7fffad9a0000 0x7fffad9c0320 librt.so.1
0x7fffad9d0000 0x7fffad9f0108 libdl.so.2
0x7fffada00000 0x7fffadc05378 libc.so.6
0x7fffadc10000 0x7fffadc54520 libpthread.so.0
0x7fffadc60000 0x7fffae5f51c8 libubsan.so.1
0x12d5e0000 0x12d6001c0 backtrace-child
TID 10644:
# 0 0x7fffadc28d48 raise
# 1 0x12d5e14a4 - 1 sigusr2
# 2 0x12d5e15cc - 1 stdarg
# 3 0x12d5e161c - 1 backtracegen
# 4 0x12d5e1648 - 1 start
# 5 0x7fffadc18c10 - 1 start_thread
# 6 0x7fffadb2d8a8 - 1 __clone
/home/mjw/wildebeest/buildbot/elfutils-fedora-ppc64le/build/tests/backtrace:
dwfl_thread_getframes: address out of range
backtrace: backtrace.c:81: callback_verify: Assertion `seen_main' failed.
./test-subr.sh: line 84: 10904 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-core.10643: no main
rmdir: failed to remove 'test-10634': Directory not empty
FAIL run-backtrace-native-core.sh (exit status: 1)
It disappeared on a rebuild...
It looks like in the failure case the child thread was unwound
correctly, but the main thread couldn't. It is unclear to be if this
was because of a bug in the unwinder or because systemd left us a bad
core file.
The corresponding change (commit 879513ab - nm: Fix file descriptor
leak on dwfl_begin failure.) really couldn't have caused this IMHO. So
it is a bit of a mystery.
Sigh,
Mark
