From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5173 invoked by alias); 25 Nov 2017 07:40:48 -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 5163 invoked by uid 89); 25 Nov 2017 07:40:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=BAYES_00,KB_WAM_FROM_NAME_SINGLEWORD,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Hx-languages-length:1663 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; Sat, 25 Nov 2017 07:40:46 +0000 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A0A22C0587C9; Sat, 25 Nov 2017 07:40:45 +0000 (UTC) Received: from host1.jankratochvil.net (ovpn-116-51.ams2.redhat.com [10.36.116.51]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8C39960F91; Sat, 25 Nov 2017 07:40:44 +0000 (UTC) Date: Sat, 25 Nov 2017 07:40:00 -0000 From: Jan Kratochvil To: Pedro Alves Cc: Simon Marchi , Keith Seitz , gdb-patches@sourceware.org Subject: ppc64 regression: [PATCH 1/2] Fix "list ambiguous_variable" Message-ID: <20171125074041.GA17197@host1.jankratochvil.net> References: <1504550858-27936-1-git-send-email-palves@redhat.com> <1504550858-27936-2-git-send-email-palves@redhat.com> <49a8a021-3d9f-c5f1-9cc4-dae1f32c7d01@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-SW-Source: 2017-11/txt/msg00649.txt.bz2 On Mon, 16 Oct 2017 17:03:18 +0200, Simon Marchi wrote: > The buildbot shows some failures on ppc64be: > > PASS -> FAIL: gdb.base/dbx.exp: whereis my_list > PASS -> FAIL: gdb.mi/gdb669.exp: -thread-list-ids > PASS -> FAIL: gdb.mi/gdb669.exp: finding MI result string > PASS -> FAIL: gdb.mi/gdb669.exp: finding number of threads in MI output > > I tested on gcc110, and bisect points to this patch here (for both tests). > A symptom of the problem is that "break main" generates two locations. > > Before (at e5f25bc5^): > > (gdb) b main > Breakpoint 1 at 0x10000560: file test.c, line 3. > (gdb) info breakpoints > Num Type Disp Enb Address What > 1 breakpoint keep y 0x0000000010000560 in main at test.c:3 > > After (at e5f25bc5) > > (gdb) b main > Breakpoint 1 at 0x10000560: main. (2 locations) > (gdb) info breakpoints > Num Type Disp Enb Address What > 1 breakpoint keep y > 1.1 y 0x0000000010000560 in main at test.c:3 > 1.2 y 0x0000000010020078
I have also hit this regression now on RHEL-7.5pre ppc64: e5f25bc5d6dba5a5c4dd36e08afd57e918c63dea is the first bad commit commit e5f25bc5d6dba5a5c4dd36e08afd57e918c63dea Author: Pedro Alves Date: Wed Sep 20 16:12:54 2017 +0100 Fix "list ambiguous_variable" echo 'main(){}'|gcc -g -x c -;./gdb -batch ./a.out -ex start Temporary breakpoint 1 at 0x10000560: file , line 1. Temporary breakpoint 1, main () at :1 1 : No such file or directory. -> Temporary breakpoint 1 at 0x10000560: main. (2 locations) Program received signal SIGSEGV, Segmentation fault. 0x7d82100810000554 in ?? () Jan