This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: global pointer current_frame query for coredump analysis
- From: Andrew Cagney <cagney at gnu dot org>
- To: "Kotian, Deepak" <Deepak dot Kotian at patni dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 01 Mar 2004 20:25:05 -0500
- Subject: Re: global pointer current_frame query for coredump analysis
- References: <374639AB1012AA4C840022842AA95BC2015ABDFD@ruby.patni.com>
Any inputs on this one, please.
Do something like:
(gdb) set debug target 1
(gdb) run
You'll see GDB fetching the information. The other place to look is
get_prev_frame.
Andrew
-----Original Message-----
From: Kotian, Deepak
Sent: Thursday, February 26, 2004 3:13 PM
To: gdb@sources.redhat.com
Subject: global pointer current_frame query for coredump analysis
Hi,
This function bactrace_commamd_1 in file stack.c calls function
like get_current_frame and get_previous_frame and then print_frame_info.
These functions use a global pointer current_frame (to a structure of
type frame_info) for displaying the backtrace.
However i am not able to track where this current_frame is filled with
unwind and register information from the core file at the lowest level.
Could one please help in this.
Thanks and Regards
Deepak