From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18005 invoked by alias); 22 Jun 2008 11:52:50 -0000 Received: (qmail 17997 invoked by uid 22791); 22 Jun 2008 11:52:49 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 22 Jun 2008 11:52:22 +0000 Received: from kahikatea.snap.net.nz (81.31.255.123.static.snap.net.nz [123.255.31.81]) by viper.snap.net.nz (Postfix) with ESMTP id 3A5043D9DBE; Sun, 22 Jun 2008 23:52:19 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 852E78FC6D; Sun, 22 Jun 2008 23:52:13 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18526.15596.855756.886158@kahikatea.snap.net.nz> Date: Sun, 22 Jun 2008 11:52:00 -0000 To: Joel Brobecker Cc: gdb@sourceware.org Subject: Re: GDB Focus Group at the 2008 GCC Summit In-Reply-To: <20080619190942.GA3744@adacore.com> References: <20080619190942.GA3744@adacore.com> X-Mailer: VM 7.19 under Emacs 22.2.50.3 X-IsSubscribed: yes 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: 2008-06/txt/msg00210.txt.bz2 > | * Next GDB Release: > | > | Lots of new features, but not ready for real release. When > | the features are in, need a little more maturing time before > | shipping it in an official release. Suggest next release > | in 6 months from now (Jan-Feb 2009). > | > | For people really interested in trying it out before the official > | release, perhaps either: > | - Announce various nightly tarballs that contain the features > | - Or perhaps create a 6.9 branch but never release 6.9. Just > | make various pre-releases 6.8.90, 6.8.91, etc. If you are talking about branching now, I think that will mean that most development will happen on the branch, i.e., there's not much point in branching. You might as well make bugfix releases, or what GDB calls respins, 6.8.1, 6.8.2 etc from the 6.8 branch. >... > | * Fix and continue: > | > | Perhaps try to implement this feature through the use of Python. > | For instance, use python to build a return value, and return that. Apple GDB already has fix and continue. Couldn't that be used as a reference implementaton? -- Nick http://www.inet.net.nz/~nickrob