From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24117 invoked by alias); 5 Jul 2004 04:35:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24105 invoked from network); 5 Jul 2004 04:35:52 -0000 Received: from unknown (HELO calvin.codito.co.in) (203.199.140.162) by sourceware.org with SMTP; 5 Jul 2004 04:35:52 -0000 Received: from [192.168.100.52] (arnor.codito.co.in [192.168.100.52]) by calvin.codito.co.in (8.12.10/8.12.10) with ESMTP id i654Vp0l032002; Mon, 5 Jul 2004 10:01:52 +0530 Message-ID: <40E8DA64.60705@codito.com> Date: Mon, 05 Jul 2004 04:35:00 -0000 From: Ramana Radhakrishnan User-Agent: Mozilla Thunderbird 0.6 (X11/20040605) MIME-Version: 1.0 To: Nagender Telkar CC: gdb@sources.redhat.com Subject: Re: Adding backtrace to an arm-based on-target debugger References: <3e59910004070417407ad2bdf8@mail.gmail.com> In-Reply-To: <3e59910004070417407ad2bdf8@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-07/txt/msg00031.txt.bz2 >I am working on developing an on-target debugger for applications on >an arm-based target. I need to add a backtrace feature to it. > >Can someone tell me where to look for the gdb serial protocol? > > 1. info gdbint. 2. gdb/remote.c >When I do a "bt" on the gdb prompt I get only the current frame. It >does not go beyond the current frame. It is as shown below. > >#0 Test_Func(nValue=525, psValueBuf=0xb00f0c, >Sending packet: $mb00ee0,4#89...Ack >Packet received: 14000000 > nValueBufSize=20) at et_amountctl.c:390 >#1 0x00d4b9e4 in ?? () > >Can you tell me what do I need to do in the target-side stub? > > > Please submit your problem with a script of your debug session showing exactly all that you did before this and a small testcase mentioning the version of gdb , gcc and binutils that you are currently using for this. You could take a look at the script command in bash or you could use emacs to capture the debug session using M-x gdb . cheers Ramana