Next: Source Prev: Stopping Up: Top

Examining the Stack

   When your program has stopped, the first thing you need to know is
where it stopped and how it got there.

   Each time your program performs a function call, the information
about where in your program the call was made from is saved in a block
of data called a "stack frame".  The frame also contains the arguments
of the call and the local variables of the function that was called.
All the stack frames are allocated in a region of memory called the
"call stack".

   When your program stops, the GDB commands for examining the stack
allow you to see all of this information.

   One of the stack frames is "selected" by GDB and many GDB commands
refer implicitly to the selected frame.  In particular, whenever you
ask GDB for the value of a variable in your program, the value is found
in the selected frame.  There are special GDB commands to select
whichever frame you are interested in.

   When your program stops, GDB automatically selects the currently
executing frame and describes it briefly as the `frame' command does
(Note: Information about a frame.).

* Frames
Stack frames
* Backtrace
* Selection
Selecting a frame
* Frame Info
Information on a frame
* MIPS Stack
MIPS machines and the function stack

automatically generated by info2www