From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9421 invoked by alias); 19 Dec 2001 21:12:08 -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 9369 invoked from network); 19 Dec 2001 21:12:05 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 19 Dec 2001 21:12:05 -0000 Received: (from mec@localhost) by duracef.shout.net (8.8.7/8.8.7) id PAA25951; Wed, 19 Dec 2001 15:11:44 -0600 Date: Wed, 19 Dec 2001 13:12:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200112192111.PAA25951@duracef.shout.net> To: ac131313@cygnus.com, aj@suse.de Subject: Re: 5.1.1 Cc: gdb@sources.redhat.com X-SW-Source: 2001-12/txt/msg00176.txt.bz2 Andreas Jaegar writes: > That would be fine. GCC has now switched using Dwarf2 as normal > debugging format and gdb 5.1 cannot read it. I haven't tried the CVS > version yet whether this is fixed. But having a gdb that can debug > programs that GCC generates would justify a 5.1.1. Happily, this has been fixed on the CVS 5.1 branch as well as the CVS mainline. My experience is that the released version of gdb 5.1 can handle dwarf2 executables produced by gcc 3.0.2, but not gcc CVS HEAD. So we are not in a horrible "latest released tools don't work together" state until gcc releases again. Some unadorned tables for the CVS 5.1 branch are here: http://www.shout.net/~mec/sunday/2001-12-06/index.html Michael C