From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89274 invoked by alias); 7 Sep 2017 18:52:03 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 89261 invoked by uid 89); 7 Sep 2017 18:52:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 07 Sep 2017 18:51:58 +0000 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2926A7E421; Thu, 7 Sep 2017 18:51:57 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2926A7E421 Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=sergiodj@redhat.com Received: from localhost (unused-10-15-17-193.yyz.redhat.com [10.15.17.193]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0173218C65; Thu, 7 Sep 2017 18:51:56 +0000 (UTC) From: Sergio Durigan Junior To: Palmer Dabbelt Cc: gdb-patches@sourceware.org, Yao Qi Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate References: Date: Thu, 07 Sep 2017 18:52:00 -0000 In-Reply-To: (Palmer Dabbelt's message of "Thu, 07 Sep 2017 10:56:34 -0700 (PDT)") Message-ID: <87lglqtk8j.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2017-09/txt/msg00188.txt.bz2 On Thursday, September 07 2017, Palmer Dabbelt wrote: > I think this wasn't my commits, as it seems to be broken as of 63c99141deff > ("remove QStartupWithShell entry from NEWS::Changes in GDB 7.11"). Also, I > haven't touched anything in aarch64 GDB land > > https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2745 > > I can't find any other mention of this on "gdb-patches", though I'm not a GDB > maintainer (we don't have a RISC-V GDB port yet) so I had to poke around the > archives and therefor may be missing something. According to here > > https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64?numbuilds=400 > > This has been broken since 34d16ea2a144 ("gdb.base/commands.exp: Test > loop_break and loop_continue in nested loops"), but that failure isn't relevant > to this one as it's a test failure not a build failure. > > https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2671 > > I poked around and there was at least one compilation failure in > between the one I just got emailed about and the test failure above, caused by > 7022349d5c86 ("Stop assuming no-debug-info functions return int"). > > https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2673/steps/compile%20gdb/logs/stdio > > Given that there's two different failures in three commits and I'm pretty sure > I didn't cause this bug, I don't want to dig through the rest of the history to > figure out what's going on. This has been broken for a while, is everyone else > just ignoring these messages? Hi Palmer, Thanks for investigating these issues. There's been a bunch of compilation errors on this builder, unfortunately. The last one is caused by commit f7000548a2b79d7e5cb924468117ca4245e6b820, from Yao. Yao, could you please take a look at the error? You can see the build logs here: https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2696/steps/compile%20gdb/logs/stdio I apologize for the wrong emails, I have found a bug in the code that determines whether the breakage email should be sent, and fixed it. Things should be more stable now. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/