RE: [ECOS] ARM Debuggers backtrace

[Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>]

Hi,

Well, gcc from cvs now generate the .debug_frame section used by the arm
debuggers.
But now there it's seems there's a bug in the Arm debugger.... 

(see http://gcc.gnu.org/ml/gcc/2001-09/msg01172.html and thread for details)

Philippe, since you work at ARM, I figured this could be a good idea if you
could tell the people in charge of the Arm debuggers (maybe in particular
the ones working on the dwarf2 stuff) that it seems they got something
wrong. 

Thanks


> -----Original Message-----
> From: Fabrice Gautier [mailto:Fabrice_Gautier@sdesigns.com]
> Subject: RE: [ECOS] ARM Debuggers backtrace
> 

> And all that to see that gcc 3 doesn't seem to handle ARM 
> call stack better
> that 2.95 ... It looks like the ARM debugger needs debug 
> symbol rather than
> frame pointers. When I "objdump" a image compiled with armcc 
> there is an
> debug_frame section, can't have it with gcc.... (see
> http://www.arm.com/support.ns4/html/sdt_debug?OpenDocument&Exp
andSection=8#_
Section8 about this "virtual stack frame" stuff )


	grmffff..

-- 
Fabrice Gautier
Software Engineer, Sigma Designs
Fabrice_Gautier@sdesigns.com