Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: sravan megan <sravan22021987@gmail.com>
To: gdb@sourceware.org
Subject: Fwd: Backtrace stopped: frame did not save the PC
Date: Mon, 19 Aug 2013 07:15:00 -0000	[thread overview]
Message-ID: <CAESop7UvR-HURs3kimaeEju=HVq+xwx21sms-OpRBszB2hsjew@mail.gmail.com> (raw)
In-Reply-To: <CAESop7Uxpo46gbxiPU9-RnvcEbnzNEOsupuWQCotE0Ev9ha_RQ@mail.gmail.com>

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


       reply	other threads:[~2013-08-19  7:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAESop7Uxpo46gbxiPU9-RnvcEbnzNEOsupuWQCotE0Ev9ha_RQ@mail.gmail.com>
2013-08-19  7:15 ` sravan megan [this message]
2013-08-19 23:33   ` Michael Eager
2013-08-20  6:24     ` sravan megan
2013-08-20 16:54       ` Michael Eager

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAESop7UvR-HURs3kimaeEju=HVq+xwx21sms-OpRBszB2hsjew@mail.gmail.com' \
    --to=sravan22021987@gmail.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox