From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 00DBF3858C53; Wed, 4 May 2022 17:44:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 00DBF3858C53 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from reform (deer0x0b.wildebeest.org [172.31.17.141]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 2A93B3000340; Wed, 4 May 2022 19:44:30 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 5625B2E80275; Wed, 4 May 2022 19:44:30 +0200 (CEST) Date: Wed, 4 May 2022 19:44:30 +0200 From: Mark Wielaard To: builder@sourceware.org Cc: "Frank Ch. Eigler" , elfutils-devel@sourceware.org Subject: Re: =?utf-8?B?4pigIEJ1aWxkYm8=?= =?utf-8?Q?t?= (GNU Toolchain): elfutils - failed test (failure) (master) Message-ID: References: <20220504153444.545A938485A5@sourceware.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220504153444.545A938485A5@sourceware.org> X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2022 17:44:35 -0000 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 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 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