From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9967 invoked by alias); 19 Aug 2013 07:15:22 -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 9954 invoked by uid 89); 19 Aug 2013 07:15:21 -0000 X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2 Received: from mail-la0-f66.google.com (HELO mail-la0-f66.google.com) (209.85.215.66) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 19 Aug 2013 07:15:20 +0000 Received: by mail-la0-f66.google.com with SMTP id er20so1606273lab.1 for ; Mon, 19 Aug 2013 00:15:18 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.22.102 with SMTP id c6mr10315163lbf.1.1376896517938; Mon, 19 Aug 2013 00:15:17 -0700 (PDT) Received: by 10.114.27.34 with HTTP; Mon, 19 Aug 2013 00:15:17 -0700 (PDT) In-Reply-To: References: Date: Mon, 19 Aug 2013 07:15:00 -0000 Message-ID: Subject: Fwd: Backtrace stopped: frame did not save the PC From: sravan megan To: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-08/txt/msg00073.txt.bz2 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) Below is a small program I tried to do a back trace at abc function void abc() { printf("Hello World\n\r"); } void abc1() { abc(); } int main() { abc1(); return 0; } (gdb) b abc Breakpoint 1 at 0x80010f94 (gdb) c Continuing. Breakpoint 1, 0x80010f94 in abc () (gdb) bt #0 0x80010f94 in abc () #1 0x80010fdc in abc1 () Backtrace stopped: frame did not save the PC 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. 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. Thanks, Sravan