From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25960 invoked by alias); 17 Oct 2017 14:34:25 -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 25891 invoked by uid 89); 17 Oct 2017 14:34:25 -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; Tue, 17 Oct 2017 14:34:20 +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 1933037E7B; Tue, 17 Oct 2017 14:34:19 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1933037E7B Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=palves@redhat.com Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by smtp.corp.redhat.com (Postfix) with ESMTP id 70BFE60603; Tue, 17 Oct 2017 14:34:18 +0000 (UTC) Subject: Re: Sporadic failures of selftest tests To: Ulrich Weigand , gdb-patches@sourceware.org References: <20171017140032.2D8AAD807C2@oc3748833570.ibm.com> <7e8c90cf-c12b-0095-16e5-3dcae94aff6f@redhat.com> From: Pedro Alves Message-ID: <39dde79f-2540-6718-8fab-e65b159fdf9f@redhat.com> Date: Tue, 17 Oct 2017 14:34:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <7e8c90cf-c12b-0095-16e5-3dcae94aff6f@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-10/txt/msg00526.txt.bz2 On 10/17/2017 03:24 PM, Pedro Alves wrote: > Now the question should be why did GDB stop there, when breakpoint 1 > was supposedly set on captured_command_loop ? > > > (gdb) break captured_command_loop > > Breakpoint 1 at 0x7117b0: file ../../binutils-gdb/gdb/main.c, line 324. > > (gdb) PASS: gdb.gdb/complaints.exp: breakpoint in captured_command_loop > ... > > (gdb) > > Breakpoint 1, captured_main (data=0x7fffffffd2e0) at ../../binutils-gdb/gdb/main.c:1147 > > 1147 captured_command_loop (); > > That seems to be the root of the problem. > > I wonder whether that's somehow related to the other Power regression > Simon reported: > https://sourceware.org/ml/gdb-patches/2017-10/msg00444.html > > I haven't managed to investigate that one. > > Does it reproduce easily for you? If so, I'd suggest a git bisect to > find the culprit. Wait, is your build of GDB an optimized build? Maybe the compiler managed to inline captured_command_loop for you? Currnetly, when GDB stops for an inline breakpoint, it stops at the stack caller, which would explain this. Thanks, Pedro Alves