From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8683 invoked by alias); 4 May 2009 16:56:16 -0000 Received: (qmail 8674 invoked by uid 22791); 4 May 2009 16:56:15 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 May 2009 16:56:10 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 90D6F2BABAC; Mon, 4 May 2009 12:56:08 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id G1ChtjZKkdML; Mon, 4 May 2009 12:56:08 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 595212BAC5D; Mon, 4 May 2009 12:56:08 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id B7B55F5900; Mon, 4 May 2009 09:56:05 -0700 (PDT) Date: Mon, 04 May 2009 16:56:00 -0000 From: Joel Brobecker To: "nagaraju.m" Cc: gdb@sourceware.org Subject: Re: back trace issue Message-ID: <20090504165605.GH26046@adacore.com> References: <49F7EF2B.4090805@redpinesignals.com> <20090429160137.GE23979@adacore.com> <49FC0D86.6090809@redpinesignals.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49FC0D86.6090809@redpinesignals.com> User-Agent: Mutt/1.5.18 (2008-05-17) 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: 2009-05/txt/msg00014.txt.bz2 Nagaraju, > I identified the function init_extraframe_info [..]-tdep.c file. I > made frame_info **prev* to point to previous frame and it is > displaying all the frame..... but it is working only when we start > the program from main (i.e when we break at main)... suppose if we > break at some function XYZ called by main then it is not working... > Is there any other file where we should provide this *prev* > information...... It's hard to help you with so little information. But the bad news is that I'm going to be either extremely busy or even unavailable in the next few weeks. Hopefully someone else might have some leads for you. In the meantime, what you can do to learn more about how things work in GDB is, if you have access to a cheap GNU/Linux machine, or even a Windows machine, is debug GDB with itself while GDB is computing a backtrace. It starts at get_prev_frame... You could compare what the working implementation does with what your implementation does, and see where things start breaking down on your side. -- Joel