From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70660 invoked by alias); 21 Aug 2015 13:22:12 -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 70649 invoked by uid 89); 21 Aug 2015 13:22:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 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 (AES256-SHA encrypted) ESMTPS; Fri, 21 Aug 2015 13:22:11 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 5DF8929332; Fri, 21 Aug 2015 09:22:09 -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 nqRLrL7AF0Yw; Fri, 21 Aug 2015 09:22:09 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 4C6C4292F3; Fri, 21 Aug 2015 09:22:09 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id CEE6C40B89; Fri, 21 Aug 2015 09:22:08 -0400 (EDT) Date: Fri, 21 Aug 2015 13:22:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: GDB 7.10 release 2015-08-21 status update Message-ID: <20150821132208.GH4571@adacore.com> References: <20150821122639.GE30455@adacore.com> <55D71C68.6040600@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55D71C68.6040600@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-08/txt/msg00573.txt.bz2 > I'm having quite an interrupted day, but I'm trying to clean up > the hacky patch a bit. Even if GDB ends up showing a couple > errors after disconnecting, like: > > You can't do that when your target is `exec' > No registers. > (gdb) > > I think it's way better than getting stuck. It's an escape hatch > for emergencies -- some bruising expected. :-) We can always clean > that up after the release, IMO. I think those sort of errors can happen > if the connection drops unexpectedly at the wrong time, even > without the patch, for instance. Indeed, that makes sense. > I agree too, especially given we've fixed the major slowness > culprit. > > > So, what do we still need to do before we can release? > > > > - Finish the work on being able to interrupt the file transfer? > > > > - There were some discussions about displaying a warning, > > and I don't see anything in the current sources; are we still > > thinking about that? > > Yes, I think so. Also Gary's QUIT patch should probably go in > as well, I think. Ah yes, I forgot about that one! Thanks, Pedro. -- Joel