From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15946 invoked by alias); 19 Aug 2013 23:33:46 -0000 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 Received: (qmail 15932 invoked by uid 89); 19 Aug 2013 23:33:45 -0000 X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.2 Received: from caibbdcaaaaf.dreamhost.com (HELO homiemail-a59.g.dreamhost.com) (208.113.200.5) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 19 Aug 2013 23:33:43 +0000 Received: from homiemail-a59.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTP id 8A06F564075; Mon, 19 Aug 2013 16:33:42 -0700 (PDT) Received: from redwood.eagercon.com (c-50-148-128-197.hsd1.ca.comcast.net [50.148.128.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: eager@eagerm.com) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTPSA id 661E156406C; Mon, 19 Aug 2013 16:33:42 -0700 (PDT) Message-ID: <5212AB55.9050203@eagerm.com> Date: Mon, 19 Aug 2013 23:33:00 -0000 From: Michael Eager User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: gdb@sourceware.org, sravan22021987@gmail.com Subject: Re: Fwd: Backtrace stopped: frame did not save the PC References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-08/txt/msg00074.txt.bz2 On 08/19/13 00:15, sravan megan wrote: > Hi All, > > I am working on Microblaze GDB (7.4.50) version. > > GDB is throwing "frame did not save the PC" error if the program is not compiled with "-g" > (debugging info) > I know that without debugging information GDB will not give complete trace information but with > out debugging info GDB should atleast give the function names. As far as I can see from your example, gdb did print the function names. You don't indicate what options were used when you compile. When you compile without optimization, MicroBlaze stores the previous frame pointer in the stack frame. With -O1, MicroBlaze does not save the frame pointer in the stack frame. > Can anyone please let me know where to look in to GDB code so that GDBcan store information of > main frame details and execute backtrace correctly. You can take a look at microblaze_analyze_prologue() in gdb/microblaze-tdep.c. The error is issued in get_prev_frame_1() in frame.c. -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077