This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: back trace issue
- From: Joel Brobecker <brobecker at adacore dot com>
- To: "nagaraju.m" <nagaraju dot m at redpinesignals dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 4 May 2009 09:56:05 -0700
- Subject: Re: back trace issue
- References: <49F7EF2B.4090805@redpinesignals.com> <20090429160137.GE23979@adacore.com> <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