From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30059 invoked by alias); 5 Jun 2014 13:58: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 30050 invoked by uid 89); 5 Jun 2014 13:58:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 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, 05 Jun 2014 13:58:47 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s55DwhTB018470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 5 Jun 2014 09:58:43 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s55Dwcro010322; Thu, 5 Jun 2014 09:58:42 -0400 Message-ID: <5390778C.3020206@redhat.com> Date: Thu, 05 Jun 2014 13:58:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Joel Brobecker CC: gdb-patches@sourceware.org Subject: Re: gdb-7.8 branching status (2014-06-04) References: <20140604171843.GX30686@adacore.com> <538F58DE.7030204@redhat.com> <20140604182038.GX4289@adacore.com> In-Reply-To: <20140604182038.GX4289@adacore.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-06/txt/msg00256.txt.bz2 On 06/04/2014 07:20 PM, Joel Brobecker wrote: >> I also filed PRs for the gdbserver regressions I had mentioned before. >> >> [Bug go/17018] New: XFAIL: gdb.go/hello.exp: Starting string check >> https://sourceware.org/PR17018 >> >> [Bug gdb/17019] New: gdb.base/restore.exp failures >> https://sourceware.org/PR17019 >> >> [Bug gdb/17020] New: gdb.base/store.exp failures >> https://sourceware.org/PR17020 >> >> [Bug gdb/17016] New: XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld rtld_map_complete >> https://sourceware.org/PR17016 >> >> [Bug gdb/17015] New: gdb.trace/collection.exp failures >> https://sourceware.org/PR17015 >> >> [Bug gdb/17014] New: gdb.trace/unavailable.exp failures >> https://sourceware.org/PR17014 >> >> Likely most of those are system/gcc related though. I'm diffing >> against a gdb.sum from a month ago, and I updated my Fedora in >> the mean time... Still, it's shame that all these are failing >> on newer systems. >> >> I'll run the testsuite on my current system against 7.7, >> diff the result against mainline, and update the PRs with >> what I find out. If they fail on 7.7 as well, they're not >> regressions, so can't be blockers. > > Thanks for doing that, Pedro. Let us know when you have the results, > so we know whether we're in the clear or not... I've done this now. I had to rerun all testing in non-parallel mode to get good diffs... The "good" news, I get all those FAILs with 7.7 too, so not regressions. Apart from the break-interp-exp crashes Markus has a fix for, and a few PASS -> XFAIL that are marked as GCC bugs, I saw this with both native and gdbserver: -PASS: gdb.cp/koenig.exp: p entry (c) +FAIL: gdb.cp/koenig.exp: p entry (c) This is: Regression for gdb.cp/koenig.exp: p entry (c) [Re: [RFA] Fix c++/16253 (tag/variable name collision)] https://sourceware.org/ml/gdb-patches/2014-04/msg00374.html I don't know the current status of that one. Keith? and this one on native: -PASS: gdb.base/pie-execl.exp: continue -PASS: gdb.base/pie-execl.exp: pie_execl_marker address second -PASS: gdb.base/pie-execl.exp: pie_execl_marker address has changed +ERROR: Process no longer exists +UNRESOLVED: gdb.base/pie-execl.exp: continue I looked at the backtrace and it's the same as with the break-interp.exp crashes, so it'll likely be fixed with Markus' patch. -- Pedro Alves