From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5598 invoked by alias); 31 Jan 2003 16:28:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 5576 invoked by uid 48); 31 Jan 2003 16:28:05 -0000 Date: Fri, 31 Jan 2003 16:28:00 -0000 Message-ID: <20030131162805.5575.qmail@sources.redhat.com> To: a.bocaniciu@computer.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: rearnsha@gcc.gnu.org Reply-To: rearnsha@gcc.gnu.org, a.bocaniciu@computer.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: debug/7032: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4 X-SW-Source: 2003-01/txt/msg01777.txt.bz2 List-Id: Synopsis: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4 State-Changed-From-To: feedback->closed State-Changed-By: rearnsha State-Changed-When: Fri Jan 31 16:28:05 2003 State-Changed-Why: While it would be nice to be able to use AXD with GCC compiled code, there's not really very much we can do here. AXD isn't a GNU-supported debugger, and GCC isn't a compiler supported by ARM for use with AXD (In reallity, AXD will probably only work with code compiled by ARM's compiler). I do understand that ARM's new debugger (RealView Debugger) is much better and handling DWARF from sources other than ARM's own compiler; and as the EABI specification for the ARM progresses, I can see interworking between debuggers becoming much more important. But in the mean time, there's little point in keeping this report open http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7032