From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id 824083858C27 for ; Sat, 28 Nov 2020 15:12:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 824083858C27 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 7DB4437251CA for ; Sat, 28 Nov 2020 16:12:25 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 3351F413CE8D; Sat, 28 Nov 2020 16:12:25 +0100 (CET) Message-ID: Subject: Re: Buildbot failure in Wildebeest Builder on whole buildset From: Mark Wielaard To: elfutils-devel@sourceware.org Date: Sat, 28 Nov 2020 16:12:25 +0100 In-Reply-To: References: <20201128041518.0EE4380071B@builder.wildebeest.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Sat, 28 Nov 2020 15:12:28 -0000 On Sat, 2020-11-28 at 14:41 +0100, Mark Wielaard wrote: > That is interesting, it only fails on the two 32bit systems. > The failure is about the specific error message returned. >=20 > FAIL: run-dwflsyms.sh > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- dwflsyms.out 2020-11-28 01:17:44.130295202 +0000 > +++ - 2020-11-28 01:17:44.140327188 +0000 > @@ -10,7 +10,7 @@ > 9: NOTYPE GLOBAL __kernel_sigtramp_rt64 (12) 0xfffb1af0418 > 10: NOTYPE GLOBAL __kernel_clock_gettime (152) 0xfffb1af0494 > 11: NOTYPE GLOBAL __kernel_get_syscall_map (44) 0xfffb1af05f4 > -ld64.so.1: No symbol table found > +ld64.so.1: Callback returned failure > 0: NOTYPE LOCAL (0) 0 > 1: SECTION LOCAL (0) 0x461b0190 > 2: SECTION LOCAL (0) 0x461b01a4 > FAIL run-dwflsyms.sh (exit status: 1) >=20 > So there is some subtle difference in the behavior of the > 'segment_report_module: Inline consider_notes() into only caller' > patch. >=20 > I haven't spotted it yet, but I suspect some 'return' from the original > function got mistranslated as a continue, break or goto out in the > inlined variant. >=20 > The specific testcase that fails is: > testrun_compare ${abs_builddir}/dwflsyms -e testfile66 --core=3Dtestfile6= 6.core >=20 > Which is a big endian ppc64 executable and core file. The issue can be replicated on x86_64 with: $ CXX=3D"g++ -m32" CC=3D"gcc -m32" ~/src/elfutils/configure --enable-mainta= iner-mode $ make -j4 $ make check TESTS=3Drun-dwflsyms.sh