6. Bdb -- Examining the Stack

Browsing
Home: | Bdb The ``Bigloo Debugger'' Nov 1999
Previous chapter: | Continuing execution after a breakpoint
Next chapter: | Using BDB under Emacs
Chapters
| Bdb Copying Conditions
1. | Table of contents
2. | Overview
3. | Running Programs Under BDB
4. | Stopping
5. | Continuing execution after a breakpoint
6. | Examining the Stack
7. | Using BDB under Emacs
| Bibliography
| Index
| When your program has stopped, the first thing you need to know is where it stopped and how it got there. All GDB commands apply here See info-file ` gdb.info', Gdb. These commands let you inspect and browse the C stack. In addition you may inspect the stack restricted to Bigloo stack frames. `` `info stack` `` `i s` Print the current stack frames. These frames may be inspected in turn with the `frame` command. `` `info args` `` `i a` Print the arguments of the selected frame, each on a separate line. `` `cinfo args` `` `ci a` If the current stack frame belongs to a Bigloo function then the arguments hold Bigloo values. The `info args` displays the Bigloo values of these arguments. In some situation it is useful to access the C representation for these arguments. This can be achieved by the `cinfo args` command that forces BDB not to interpret the current function as a Bigloo function. `` `info locals` `` `i l` Print the local variables of the selected frame, each on a separate line. `` `cinfo locals` `` `ci a` Print the local variables as if they were C variables, each on a separate line.

This Scribe page has been generated by `scribeinfo`.
Last update Tue Dec 16 13:46:42 2003