From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20593 invoked by alias); 8 Jan 2004 15:14:23 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 20498 invoked from network); 8 Jan 2004 15:14:18 -0000 Received: from unknown (HELO mwinf0804.wanadoo.fr) (193.252.22.23) by sources.redhat.com with SMTP; 8 Jan 2004 15:14:18 -0000 Received: from takamaka.act-europe.fr (AStDenis-101-1-4-29.w80-13.abo.wanadoo.fr [80.13.18.29]) by mwinf0804.wanadoo.fr (SMTP Server) with ESMTP id B20091800100; Thu, 8 Jan 2004 16:14:15 +0100 (CET) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id D83C247D62; Thu, 8 Jan 2004 19:14:12 +0400 (RET) Date: Thu, 08 Jan 2004 15:14:00 -0000 From: Joel Brobecker To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: GDB 6.1 branch end jan? Message-ID: <20040108151412.GA8144@gnat.com> References: <3FFC98E8.8010001@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FFC98E8.8010001@gnu.org> User-Agent: Mutt/1.4i X-SW-Source: 2004-01/txt/msg00087.txt.bz2 > GDB 6.1 is ment to branch sometime in January. Now that the SPARC > rewrite has been merged (and SPARC is looking really healthy, go mark!) > its time to come up with a more concrete set of dates. Let's try: > > ~branch 2004-01-31 > ~release 2004-03-15 I think it'd be nice if the following patch made it for 6.1: http://sources.redhat.com/ml/gdb-patches/2003-11/msg00468.html This patch adds support for DW_TAG_subrange_type DIEs that are emitted by GCC for some Ada types (modular types, and also enumeration subtypes). Admitedly Ada support has not been merged in yet, but this prevents I think an error that causes at least a complaint, and maybe even an internal error (don't remember anymore). (there are actually 2 patches: Andreas' and mine - mine is a bit more complete than Andreas', but that may be unnecessary completeness. I implemented it half mechanically, and was content when I found that it worked :). -- Joel