From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82152 invoked by alias); 11 Jan 2019 21:31:36 -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 82138 invoked by uid 89); 11 Jan 2019 21:31:35 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:2741, online X-HELO: mailsec101.isp.belgacom.be Received: from mailsec101.isp.belgacom.be (HELO mailsec101.isp.belgacom.be) (195.238.20.97) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 11 Jan 2019 21:31:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skynet.be; i=@skynet.be; q=dns/txt; s=securemail; t=1547242292; x=1578778292; h=message-id:subject:from:to:date:in-reply-to:references: mime-version:content-transfer-encoding; bh=NiaqDsBnY3hStsKX80V/Zt47Qmo9Mp4AXFJAiES+b9c=; b=TYDVk1RzUugQi2t4EHmczg73M/hxWEdTEh8uW2ijthjoi/rK9McRq5pf MC7lTKdgStyUTjzioRQL6DJ4YMynLw==; Received: from 184.205-67-87.adsl-dyn.isp.belgacom.be (HELO md) ([87.67.205.184]) by relay.skynet.be with ESMTP/TLS/AES256-GCM-SHA384; 11 Jan 2019 22:31:30 +0100 Message-ID: <1547242289.5979.3.camel@skynet.be> Subject: Re: GDB 8.3 release -- 2019-01-11 update From: Philippe Waroquiers To: Joel Brobecker , gdb-patches@sourceware.org, tom@tromey.com Date: Fri, 11 Jan 2019 21:31:00 -0000 In-Reply-To: <20190111095332.GB22922@adacore.com> References: <20190111095332.GB22922@adacore.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00258.txt.bz2 On Fri, 2019-01-11 at 13:53 +0400, Joel Brobecker wrote: > Hello again, > > New update for the GDB-8.3 release. Reminder: The target date > for creating the branch is: > > Tue Jan 15th > > The wiki page for tracking known issues is at: > > https://sourceware.org/gdb/wiki/GDB_8.3_Release > > Fixed since the last update: > > * [JoelB] > GDB crash re-running program on Windows > > Fix in review: > https://www.sourceware.org/ml/gdb-patches/2018-12/msg00443.html > > * [KeithS] gdb/23712 (**inherited from 8.2.1**) > dw2_add_symbol_to_list language assertion > > https://www.sourceware.org/ml/gdb-patches/2019-01/msg00231.html > Well done, Keith, and thanks to everyone who participated in > all the discussions! > > * [SimonM] gdb/23893 > Search paths for debug files for remote debuggee checks are broken > https://sourceware.org/bugzilla/show_bug.cgi?id=23893 > > Known blocking issues: > > * [TomT/Joel] > GDB UI word wrapping broken/interferes with 'set style' > https://www.sourceware.org/ml/gdb-patches/2018-12/msg00435.html > https://www.sourceware.org/ml/gdb-patches/2019-01/msg00098.html > > From what I can tell, "set style enabled off" doesn't prevent > the problem from happening either. Tom indicated in his last > message he has a fix, and just needs a testcase. I did some manual test in a corner with the patch. The patch improves significantly, but there are still one or two things not ok (see msg00098.html thread). Regarding the style, it would be really nice to have: https://sourceware.org/ml/gdb-patches/2018-12/msg00449.html as otherwise, set|show style online help/behaviour is inconsistent with the other set|show. It would be nice to have https://sourceware.org/ml/gdb-patches/2019-01/msg00227.html (as GDB will color more file names, functions and addresses). Thanks Philippe > > I will try to run it against AdaCore's testsuite, which hit > that issue quite a bit, so probably a good testbed too. > > Looking at the PRs marked 8.3 as the milestone, I also see... > > * [TomT] tui/20819 > Binding Control-j in inputrc breaks "layout asm" > https://sourceware.org/bugzilla/show_bug.cgi?id=20819 > > ... but i don't understand why this would be blocking for 8.3. > It would be nice to have a way to get a more detailed history > of the changes made to the status of that PR so we can determine > when it was marked 8.3. My suspicion is that it was marked 8.3 > when fixed by Tom, and then the PR got re-opened (around Jan 2nd) > due to a regression. > > Tom - do you confirm this is not a critical bug, other than > maybe the regression, in which case it would be sufficient to > simply revert? > > Any other issue, please let us know... > > Thank you!