This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: debug/7032: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4
- From: rearnsha at gcc dot gnu dot org
- To: a dot bocaniciu at computer dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: 31 Jan 2003 16:28:05 -0000
- Subject: Re: debug/7032: arm-elf-gcc 3.1 generates wrong DWARF-2, unlike 3.0.4
- Reply-to: rearnsha at gcc dot gnu dot org, a dot bocaniciu at computer dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
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