From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 125974 invoked by alias); 20 Mar 2017 22:39:15 -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 125942 invoked by uid 89); 20 Mar 2017 22:39:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=slowly, U*brobecker, sk:brobeck, D*adacore.com X-HELO: mail-qk0-f175.google.com Received: from mail-qk0-f175.google.com (HELO mail-qk0-f175.google.com) (209.85.220.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 20 Mar 2017 22:39:13 +0000 Received: by mail-qk0-f175.google.com with SMTP id 1so122505444qkl.3 for ; Mon, 20 Mar 2017 15:39:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=lQJjc90M5L7XbKnSjZpkdhQzZjaKq1SHZJZrBGMQq3o=; b=nx3ZknzNV3KhFY2aEfHAvXQOTVVSUREl0GkfkywTRA6GRxLOMZs50uTp6H5s+UMC/L 4Oyi7flNaJt9icFnd6cv+EnLBe5/tOBvZQrQdw6GzAxxy0aXPtKkVzWT1s8vv+U0W8Qm yov0PF2IqMYFSniojKyTf8F1ErPstf+B8RKS/MQKm1BEvdi7X+brmhN9aw1rW2wQX00d ULqejo7pEK6i2LTjUKgImASBRJPD6flcCy3nNasfJu9y01pL8ybpzEOBy+F11Z5A3jAN tEVBspGhxVbgWtfFOKcUdR0CWPguhvmGdm9c7nG4budQRlTCtmLR76ecPQw3EKQN9bMz QGpA== X-Gm-Message-State: AFeK/H13nukDWZN4fYBzDRsvA6gD+8b7ERxX4yjAfwZ6/UxiN0RcnsDLoLvKE1iggxRBHJjdelUOvIYIrVxvHA== X-Received: by 10.55.41.215 with SMTP id p84mr26239993qkp.35.1490049552407; Mon, 20 Mar 2017 15:39:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.140.130 with HTTP; Mon, 20 Mar 2017 15:39:12 -0700 (PDT) In-Reply-To: <20170320201629.pbjzaqsnvs7dx7f2@adacore.com> References: <20170320201629.pbjzaqsnvs7dx7f2@adacore.com> From: Yao Qi Date: Mon, 20 Mar 2017 22:39:00 -0000 Message-ID: Subject: Re: GDB 8.0 release/branching 2017-03-20 update To: Joel Brobecker Cc: "gdb-patches@sourceware.org" , Nitish Kumar Mishra , Tremblay , Keith Seitz , "Wiederhake, Tim" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-03/txt/msg00356.txt.bz2 On Mon, Mar 20, 2017 at 8:16 PM, Joel Brobecker wro= te: Hi Joel, Tim contacted me off-list that his work site will relocate at the end of march and he will not be able to respond to mails or work on the patches. It may take two weeks, and I am not sure he has been unreachable from now on. > * [TimWiederhake] new "record" Python API should be finalized before we r= elease > (otherwise, we might be have a compatibility issue if we don't design > them well from the start) > > https://sourceware.org/ml/gdb-patches/2017-03/msg00023.html > > Looks like the discussion is still fairly active, and I am starti= ng > to think that we might be putting too much pressure to get this d= one > before 8.0. > > What's the status of this API? Is this something entirely new? > Or something that replaces an API which was already contributed? They are new python APIs. > If it's a replacement, was the older API part of a previous relea= se? > Looking at the NEWS file, it looks like it's something which > would be new. So we could decide to not rush this into 8.0, > and wait for 8.1, when we're more certain of the API we'd like. > It would also give it another 6 months of use where we can > easily change the API, before it's part of a release, and therefo= re > harder to change. I've started reading this new APIs and the code since late last week. Progress slowly as I know little about GDB python. I gradually understand the code, and do some experiments to make sure my suggestions can be done. I want to re-design the APIs, to make them more general, less btrace specific. I'll post my design draft tomorrow, then people can compare the current design to mine. If we think we need to improve the current design, it is unlikely to get it done by 8.0. > > * [TimWiederhake] Build issue when using Python 2.6.x > > What's the status of that patch? My questions were answered, > but was the patch reviewed? > > https://www.sourceware.org/ml/gdb-patches/2017-03/msg00053.html > I've already conditionally approved the patch, with a fix in doc part, "Python 3" or "@code{Python} 3". Tim's patch uses the former but I suggested the latter. Tim believes "Python 3" should be used (off-list) so I asked Eli https://sourceware.org/ml/gdb-patches/2017-03/msg00334.html --=20 Yao (=E9=BD=90=E5=B0=A7)