From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7424 invoked by alias); 19 May 2016 15:21:19 -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 7409 invoked by uid 89); 19 May 2016 15:21:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=constantly, fuller, succession, our 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 (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 19 May 2016 15:21:15 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 797E4C04D283; Thu, 19 May 2016 15:21:14 +0000 (UTC) Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u4JFLD21009479; Thu, 19 May 2016 11:21:13 -0400 Subject: Re: gdb-7.11.1 - 2 weeks to go... To: Joel Brobecker , gdb-patches@sourceware.org References: <20160510161756.GB26324@adacore.com> From: Pedro Alves Message-ID: <395c33b0-7071-ed80-915a-dd8dbefe2786@redhat.com> Date: Thu, 19 May 2016 15:21:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160510161756.GB26324@adacore.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SW-Source: 2016-05/txt/msg00339.txt.bz2 On 05/10/2016 05:17 PM, Joel Brobecker wrote: > Hello everyone, > > Just a quick update on this 7.11.1 release - our target release date > is about 2 weeks away. As far as I can tell from looking at... > > https://sourceware.org/gdb/wiki/GDB_7.11_Release > > ... we have 2 open PRs: > > * Bug 19828 - 7.11 regression: non-stop gdb -p container>: internal error > > Looks already fixed on master, so there is a chance we might > be able to fix that on the branch soon. > Odd, it definitely doesn't work for me on master. This is the one that I said in the other status thread that I had a patch for, but that it surprisingly caused regressions in the attach-many-short-lived-threads.exp testcase. I finally managed to find some time to stare at "set debug infrun" logs, and wrote (I think) a full fix, here: [PATCH 0/6] Fix PR gdb/19828 (attach -> internal error) and attach optimizations https://sourceware.org/ml/gdb-patches/2016-05/msg00335.html That's a bit ... invasive ... I have a simpler version too, which is being carried by Fedora for a few weeks without reports of problems: [PATCH/7.11.1?] Simpler fix PR gdb/19828: gdb -p : internal error https://sourceware.org/ml/gdb-patches/2016-05/msg00335.html ... though that's not as comprehensive as the bigger series. It leaves "attach&" (background attach) broken... I haven't heard complaints about that so far; maybe nobody uses that command... Another option that just occurred to me, is to apply the fuller fix to the branch (patch #6 in the series), and disable the attach-many-short-lived-threads.exp test in the branch? GDB regresses in the use case of attaching to a program that is constantly spawning many threads in quick succession, though that's a contrived use case to expose problems. Probably no program in the wild is like that. I hope. Use cases like Go programs with tons of goroutines make me worry a bit. Thanks, Pedro Alves