From: Mark Wielaard <mark@klomp.org>
To: builder@sourceware.org
Cc: "Frank Ch. Eigler" <fche@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Wed, 4 May 2022 19:44:30 +0200 [thread overview]
Message-ID: <YnK7fiNcAnSaipMU@wildebeest.org> (raw)
In-Reply-To: <20220504153444.545A938485A5@sourceware.org>
Hi,
On Wed, May 04, 2022 at 03:34:44PM +0000, builder--- via Elfutils-devel 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/17
>
> Build state: failed test (failure)
> Revision: 59158656f3b0b99d8784ddc82c15778813000edc
> Worker: debian-armhf
> Build Reason: (unknown)
> Blamelist: Frank Ch. Eigler <fche@redhat.com>
Hmmmm.... This seems totally unrelated to that commit
> - 7: make check ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/6/builds/17/steps/7/logs/stdio
> - test-suite.log: https://builder.sourceware.org/buildbot/#builders/6/builds/17/steps/7/logs/test-suite_log
FAIL: run-backtrace-native-core.sh
==================================
0xbeb25000 0xbeb26000 linux-vdso.so.1
0xb6f70000 0xb6f99974 ld-linux-armhf.so.3
0xb626e000 0xb62e8078 libm.so.6
0xb62e9000 0xb63f36ec libstdc++.so.6
0xb63f4000 0xb6409218 librt.so.1
0xb640a000 0xb641c0c4 libdl.so.2
0xb641d000 0xb651633c libc.so.6
0xb6517000 0xb653b270 libpthread.so.0
0xb653c000 0xb6564134 libgcc_s.so.1
0xb6565000 0xb6a130f4 libubsan.so.1
0xb6a14000 0xb6f6fe30 libasan.so.5
0x410000 0x4227c0 backtrace-child
TID 25080:
# 0 0xb6526526 __libc_do_syscall
# 1 0xb6525316 - 1 raise
# 2 0x411290 - 1 sigusr2
# 3 0x411344 - 1 stdarg
# 4 0x411378 - 1 backtracegen
# 5 0x411382 - 1 start
# 6 0xb651cbbe - 1 start_thread
# 7 0xb64b716c - 1 <null>
TID 25076:
# 0 0xb64b48d2 syscall
# 1 0xb6a50adc - 1 __interceptor_pthread_create
/var/lib/buildbot/workers/wildebeest/elfutils-debian-armhf/build/tests/backtrace: dwfl_thread_getframes: no matching address range
/var/lib/buildbot/workers/wildebeest/elfutils-debian-armhf/build/tests/backtrace: dwfl_thread_getframes: No DWARF information found
backtrace: backtrace.c:81: callback_verify: Assertion `seen_main' failed.
./test-subr.sh: line 84: 25096 Aborted LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH" $VALGRIND_CMD "$@"
/var/lib/buildbot/workers/wildebeest/elfutils-debian-armhf/build/tests/backtrace: dwfl_thread_getframes: No DWARF information found
backtrace-child-core.25076: arm needs debuginfo installed for all libraries
rmdir: failed to remove 'test-25065': Directory not empty
FAIL run-backtrace-native-core.sh (exit status: 1)
I wonder if this is caused by the asan or ubsan "interceptor". But if
so, why haven't we seen this before?
Cheers,
Mark
next prev parent reply other threads:[~2022-05-04 17:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 15:34 builder
2022-05-04 17:44 ` Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-14 2:51 builder
2022-12-21 18:22 builder
2022-12-19 23:56 builder
2022-12-12 14:31 builder
2022-11-28 13:30 builder
2022-11-04 22:29 builder
2022-11-03 15:27 builder
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard
2022-11-02 1:15 builder
2022-11-02 12:06 ` Mark Wielaard
2022-11-01 21:28 builder
2022-10-31 13:51 builder
2022-10-27 19:25 builder
2022-10-17 14:59 builder
2022-10-17 9:08 builder
2022-10-17 10:26 ` Mark Wielaard
2022-10-17 11:02 ` Frank Ch. Eigler
2022-10-17 14:09 ` Frank Ch. Eigler
2022-10-16 21:02 builder
2022-10-16 15:47 builder
2022-10-16 16:26 ` Mark Wielaard
2022-10-13 16:51 builder
2022-09-14 19:36 builder
2022-07-31 23:54 builder
2022-08-01 0:09 ` Mark Wielaard
2022-08-01 9:13 ` Mark Wielaard
2022-05-28 9:15 builder
2022-05-28 9:35 ` Mark Wielaard
2022-05-28 9:43 ` Mark Wielaard
2022-06-02 15:44 ` Mark Wielaard
2022-05-27 16:02 builder
2022-05-27 22:30 ` Mark Wielaard
2022-05-28 2:34 ` Frank Ch. Eigler
2022-05-28 9:04 ` Mark Wielaard
2022-05-14 15:34 builder
2022-05-14 16:40 ` Mark Wielaard
2022-05-14 14:42 builder
2022-04-23 13:19 builder
2022-04-23 1:19 builder
2022-04-23 1:31 ` Mark Wielaard
2022-04-19 9:05 builder
2022-04-19 9:28 ` Mark Wielaard
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=YnK7fiNcAnSaipMU@wildebeest.org \
--to=mark@klomp.org \
--cc=builder@sourceware.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).