From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27386 invoked by alias); 16 Jan 2009 03:40:35 -0000 Received: (qmail 27375 invoked by uid 22791); 16 Jan 2009 03:40:33 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Jan 2009 03:39:58 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 484042A96AC; Thu, 15 Jan 2009 22:39:56 -0500 (EST) 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 1RujL7efDkxj; Thu, 15 Jan 2009 22:39:56 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 7DEE22A9681; Thu, 15 Jan 2009 22:39:55 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 770DFE7ACD; Fri, 16 Jan 2009 07:39:48 +0400 (RET) Date: Fri, 16 Jan 2009 03:40:00 -0000 From: Joel Brobecker To: teawater Cc: David Daney , gdb@sourceware.org Subject: Re: Discussing the next GDB release (GDB 7.0?) Message-ID: <20090116033948.GI31296@adacore.com> References: <20090115034552.GF24105@adacore.com> <496F7115.9010903@caviumnetworks.com> <20090115173646.GC31296@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-01/txt/msg00086.txt.bz2 Hi Teawater, > > Do we need process record and replay in 7.0 release? > > It's in submit process. > And catch syscall? I think it hang too. Neither of these features seem critical to me, but that's only a personal opinion. As GDB Maintainer, I think of my role as being the technician that implements the recommendations of the GDB Maintainers. If the maintainers think this is critical, then I'll add them to the list as blocking for the release. That being said, this does not mean that they will not make it for the release. If they get checked in before we branch, then they're in... Regarding the "process record" series of patches, I hesitate to review them, because I know there has been some discussion that I had to zap because I was too busy at the time. Hopefully the persons involved in the discussion at the time can also review your patches. If not, I'll be home by the end of the month - could you send me personally the links to the discussions and the patches, and I'll try to take a look. Regarding the "catch syscall", same thing. There was a long debate, and I zappped it. Same suggestion. -- Joel