From: Joel Brobecker <brobecker@adacore.com>
To: "nagaraju.m" <nagaraju.m@redpinesignals.com>
Cc: gdb@sourceware.org
Subject: Re: back trace issue
Date: Mon, 04 May 2009 16:56:00 -0000 [thread overview]
Message-ID: <20090504165605.GH26046@adacore.com> (raw)
In-Reply-To: <49FC0D86.6090809@redpinesignals.com>
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
next prev parent reply other threads:[~2009-05-04 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 7:53 nagaraju.m
2009-04-29 17:01 ` Joel Brobecker
[not found] ` <49FC0D86.6090809@redpinesignals.com>
2009-05-04 16:56 ` Joel Brobecker [this message]
2009-04-29 18:29 ` Anthony Berent
2009-05-02 9:21 nagaraju.m
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=20090504165605.GH26046@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=nagaraju.m@redpinesignals.com \
/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