RE: Gcc 3.0 and ARM Stackframe

[Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>]

Well, I've tried gcc 3.01 and it doesn't output .debug_frame section
neither.

I've looked a bit in the code and it seems that all the code is already
there to output this section. I've hacked gcc to see if it was indeed
calling this code, and it is. So i don't understand really why there's no
.debug_frame section in my final image (arm-elf target, -g and even
-gdwarf-2 at compile time).

I've traced gcc all the way down to dwarf2out_frame_debug_expr which is
called 11 times in my smallish test program.

I'm thinking that maybe everything is computed but the section is not
written in the file at the end of the compilation.But I can't find where
this happen. Can somebody help me

Thanks

>  -----Original Message-----
> From: 	Fabrice Gautier  
> Sent:	Tuesday, September 25, 2001 10:45 AM
> To:	'gcc@gcc.gnu.org'
> Subject:	Gcc 3.0 and ARM Stackframe
> 
> Hi,
> 
> When compiling with gcc 2.95 for ARM, it's not possible to 
> have the ARM debugger display the call stack (or backtrace as 
> they say) I saw a message about the problem, syaing it was 
> because gcc was not generating proper stack frame. (However 
> gdb seems to display the call stack, go figure...)
> 
> As there is a new ARM backend in Gcc 3.0, I would like to 
> know if this new backend generate proper stack frame for the 
> ARM debugger ?
> 
> Thank you,
> 
> -- 
> Fabrice Gautier
> Software Engineer, Sigma Designs
> Fabrice_Gautier@sdesigns.com
>