Re: Adding backtrace to an arm-based on-target debugger

[Nagender Telkar <ntelkar at gmail dot com>]

Hi Atul,

The type of applications I am trying to debug using my arm-based stub
are compiled with arm-elf-gcc. But these applications make certain
system calls to an underlying module, which happens to be compiled
using armcc.

Another important point is that the application(compiled in
arm-elf-gcc) and the underlying module(compiled in armcc) make use of
the same stack.

So, when I do a "bt" on the gdb prompt, the gdb has to parse the stack
that contains symbols of both the arm-elf-gcc compiled code and the
arm-cc compiled code. Can the gdb do that?

Regarding the gdb documentation, I find only description of the
symbols(c, n, g etc) that are used but not the actual protocol or the
actual handshaking mechanism, that is, I want to know what happens
after you do a bt, s or a c on the gdb prompt. Is the series of
requests that the gdb makes to the stub documented?

Thanks in advance,
Nagender


On Thu, 8 Jul 2004 10:54:42 +0530, Atul Talesara
<atul.talesara@nevisnetworks.com> wrote:
> Thought this might help you ...
> http://www.embedded.com/1999/9911/9911feat3.htm
> 
> Regards,
> Atul P Talesara
> ----------------------------------------------------------
> Be not afraid of life. Believe that life is worth living,
> and your belief will help create the fact."
>                                            - Henry James
> ----------------------------------------------------------
> 
> -----Original Message-----
> From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com]
> On Behalf Of Nagender Telkar
> Sent: Thursday, July 08, 2004 1:55 AM
> To: Ramana Radhakrishnan
> Cc: gdb@sources.redhat.com
> Subject: Re: Adding backtrace to an arm-based on-target debugger
>