From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37065 invoked by alias); 21 Sep 2016 17:16:54 -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 37026 invoked by uid 89); 21 Sep 2016 17:16:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=traveling, our, Don X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 21 Sep 2016 17:16:43 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 3203E116C25; Wed, 21 Sep 2016 13:16:42 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id A9QRpK4dYYMK; Wed, 21 Sep 2016 13:16:42 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A5A83116C1E; Wed, 21 Sep 2016 13:16:41 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 0410B42320; Wed, 21 Sep 2016 10:16:40 -0700 (PDT) Date: Wed, 21 Sep 2016 17:17:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Cc: t@adacore.com, donb@codesourcery.com, Pedro Alves , Yao Qi , antoine.tremblay@ericsson.com Subject: GDB 7.12 release - 2016-09-21 update? Message-ID: <20160921171639.GB3842@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2016-09/txt/msg00261.txt.bz2 Hello everyone, Sorry for being radio-silent the last few weeks. It's been a combination of a crazy traveling schedule, and that thing we call "work"... Anyways, I reviewed the list of PRs marked as targetting 7.12, as well as the items listed in our 7.12 release page (https://sourceware.org/gdb/wiki/GDB_7.12_Release). It looks like we may have a ways to go before being able to release. Here are my thoughts on each of them. What do you guys think? PR 20395: -var-update gives incorrect register values for frames 1 and above Assigned to: Don Breazeal Status: Patch proposed, but not sure it is good. Proposed as blocker for 7.12 because incorrect data is returned. However, not sure whether I agree or not yet. I think a better question to ask would be: Is it a regression compared to 7.11? PR 20448: target descriptions: bitfields vs flags backward/forward incompatible change Assigned to: *** UNASSIGNED *** Status: ??? This is an actual regression, so I agree we should try to get this fixed for 7.12. Is anyone working on this? PR 20627: GDBserver can not be closed Assigned to: *** UNASSIGNED *** Status: ??? Not sure if this is a regression or not, and whether it is actually critical for 7.12. If there is no data loss, perhaps we can just document the workaround. Yao? PR 20487: Thread sync broken between mi and cli with new-ui command Assigned to: Antoine Tremblay Status: Fix in progress Not sure if this is really blocking for 7.12 either as it relates to a new feature. But since we seem to be close to a resolution, and this makes the new feature more usable, perhaps we can try to have it in 7.12. Otherwise, perhaps release 7.12 with this limitation in the release notes, and fix it for 7.12.1??? PR 11094: cannot reexecute programs using the GDB JIT interface in shared libs Assigned to: Pedro Alves Status: Fix posted. I don't think it's the reported issue itself that was the cause of making this PR blocking for 7.12, but rather the SEGV that was detected after the patch was pushed in. The fix was posted, so I suspect we can have a quick resolution for this one. PR 20609 gdb --pid $(pidof qemu-system-x86_64) stopped working with gdb 7.11.1 Assigned to: *** UNASSIGNED *** Status: ??? As hinted by the subject, this is a real regression, and the problem description says that this leads to a non-functional session. Is anyone working on this? Thanks! -- Joel