4. Bdb -- Stopping

4. Bdb -- Stopping

Browsing

Home: Bdb
The ``Bigloo Debugger''
Nov 1999

Previous chapter: Running Programs Under BDB
Next chapter: Continuing execution after a breakpoint

Stopping

4.1 Setting breakpoints
4.2 Break conditions

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

In addition to the GDB commands, BDB enables breakpoints inside Bigloo source code
4.1 Setting breakpoints

You may use any of the GDB commands to set breakpoints The key point is that none of these commands know Bigloo identifiers. Setting breakpoints inside Bigloo functions requires special BDB commands:

break FUNCTION
b FUNCTION
Set a breakpoint at entry to the function FUNCTION. IF FUNCTION is an uppercase symbol, FUNCTION is interpreted as the name of a Bigloo function. If FUNCTION contains at least one lower case character it is interpreted as the name of a C function.

tbreak FUNCTION
tb FUNCTION
Set a temporary breakpoint at entry to the function FUNCTION.

4.2 Break conditions

Conditions may be associated with breakpoints inside debugged code. The syntax is:

bcond BNUM EXPRESSION
Specify EXPRESSION as the break condition for breakpoint number BNUM. EXPRESSION is an expression that is evaluated in the environment of the breakpoint. That is EXPRESSION may uses local variables. If EXPRESSION is made of uppercase symbols, it is interpreted as a Bigloo expression and is thus evaluated by the Bigloo interpreter. Otherwise it is interpreted as a C expression.

This Scribe page has been generated by scribeinfo.
Last update Mon Mar 15 17:17:13 2004