From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19634 invoked by alias); 2 Sep 2009 17:18:34 -0000 Received: (qmail 19624 invoked by uid 22791); 2 Sep 2009 17:18: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; Wed, 02 Sep 2009 17:18:25 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 46DED2BAB59; Wed, 2 Sep 2009 13:18:22 -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 5G7vbjh6r35s; Wed, 2 Sep 2009 13:18:22 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 11EE92BAB31; Wed, 2 Sep 2009 13:18:22 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 06840F589A; Wed, 2 Sep 2009 10:18:14 -0700 (PDT) Date: Wed, 02 Sep 2009 17:18:00 -0000 From: Joel Brobecker To: Jack Howarth Cc: gdb@sourceware.org Subject: Re: [gdb-7.0 release] 2009-09-02 status and proposed plan Message-ID: <20090902171813.GS4379@adacore.com> References: <20090902164425.GR4379@adacore.com> <20090902170908.GA5175@bromo.med.uc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090902170908.GA5175@bromo.med.uc.edu> User-Agent: Mutt/1.5.18 (2008-05-17) 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-09/txt/msg00025.txt.bz2 > Is there any chance that x86_64-apple-darwin10 could be added > to the supported targets? The current gdb cvs builds on that > target, but can't debug binaries... > > http://sourceware.org/ml/gdb/2009-08/msg00270.html If we manage to follow the schedule that I proposed, I think that the changes for this to happen are slim. For this to make it to 7.0, you'll need to either fix it or find someone to fix it, and then have it approved for inclusion. Having said that, This is typically the type of fix that can be checked in a branch - unless the change is really intrusive, that is. The actual release date is about 3 weeks away, and I propose to also make a corrective release in December. That gives you a little more time to get this fixed. -- Joel