From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1189 invoked by alias); 23 Apr 2008 11:30:48 -0000 Received: (qmail 1174 invoked by uid 22791); 23 Apr 2008 11:30:47 -0000 X-Spam-Check-By: sourceware.org Received: from mail.ashling.com (HELO ashling.com) (62.77.186.162) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 23 Apr 2008 11:30:27 +0000 Received: from Syam ([192.168.10.57]) by ashling.com (ashling.com [127.0.0.1]) (MDaemon PRO v9.6.5) with ESMTP id md50000997534.msg for ; Wed, 23 Apr 2008 12:30:22 +0100 X-Spam-Processed: ashling.com, Wed, 23 Apr 2008 12:30:22 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 192.168.10.57 X-Return-Path: jiju.george@nestgroup.net X-Envelope-From: jiju.george@nestgroup.net X-MDaemon-Deliver-To: gdb@sources.redhat.com From: "Jiju George T" To: "'Vladimir Prus'" , References: <005101c8a52a$13f76910$390aa8c0@ashmicro.ashling.com> Subject: RE: clearing call stack when a new binary file is loaded Date: Wed, 23 Apr 2008 12:57:00 -0000 Message-ID: <009201c8a535$6a62f8e0$390aa8c0@ashmicro.ashling.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MDAV-Processed: ashling.com, Wed, 23 Apr 2008 12:30:24 +0100 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00200.txt.bz2 I am using a cross compiled version of GDB for MIPS architecture (mipsel-linux-gdb) compiled using cross tools. It is based on GNU GDB version 6.6 Thanks, Jiju -----Original Message----- From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On Behalf Of Vladimir Prus Sent: 23 April 2008 11:52 To: gdb@sources.redhat.com Subject: Re: clearing call stack when a new binary file is loaded Jiju George T wrote: > Hi, > > We are developing a graphical embedded debugger based on GDB mi interface. > UI part is based on Eclipse CDT and it communicates with GDB through mi > interface. We are facing a problem with call stacks after a new binary is > loaded to GDB. Our UI relays on the call stack information provided by GDB > to show the debug context. > > Steps to reproduce the issues: > > 1) Start GDB and connect to remote GDB server which is connected to an > embedded target. The embedded target is waiting at PC 0xBFC00000 > 2) Now load an ELF file to GDB with entry point as 0xA0000000 > 3) Now GDB shows $pc register value as 0xA0000000. But the call stack > still shows frames with 0xBFC00000 > > > Is this GDB behaviour by design? Is there any mi interface to clear the > stack frame and update to the current $pc value? Which version of GDB? - Volodya