This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ARM Debuggers backtrace
- To: 'Jonathan Larmour' <jlarmour at redhat dot com>
- Subject: RE: [ECOS] ARM Debuggers backtrace
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Tue, 25 Sep 2001 13:00:34 -0700
- Cc: "Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
> -----Original Message-----
> From: Jonathan Larmour [mailto:jlarmour@redhat.com]
> Sent: Tuesday, September 25, 2001 12:40 PM
> To: Fabrice Gautier
> Cc: Ecos-List (E-mail)
> Subject: Re: [ECOS] ARM Debuggers backtrace
>
>
> Fabrice Gautier wrote:
> > >
> > > > I'm not sure if gdb is abble to display call stack but ARMs
> > > > debugger is not able to do so, at least on a default build.
> > >
> [snip]
> > So gcc + gdb works and armcc + ARM debugger works but not gcc + ARM
> > debugger... too bad...going to ask some gcc/gdb mailing lists.
>
> Try compiling with -mapcs-frame if you haven't already.
Already tried (correct --apcs-frame to -mapcs-frame in my first mail)
This is apparently a known problem, saw something about gcc-2.95 not
generating correct stack frames for Arm debugger. A look at the assembly
shows that the generated code is actualy quite different.
But i'm now trying to see if GCC 3 solved the problem (there is a new ARM
back end in Gcc 3 so maybe...) but i've got some difficulties building gcc
3...
Thanks
--
Fabrice Gautier
Software Engineer, Sigma Designs
Fabrice_Gautier@sdesigns.com