Previous: Breakpoint Information, Up: Intro to Breakpoints
Besides source and procedural breakpoints, Guile includes an early implementation of a third class of breakpoints: range breakpoints. These are breakpoints that trigger when program execution enters (or perhaps exits) a defined range of source locations.
Sadly, these don't yet work well. The apparent problem is that the
extra methods for set-breakpoint!
and get-breakpoint
cause
some kind of explosion in the time taken by GOOPS to construct its
method cache and to dispatch calls involving these generic functions.
But we haven't really investigated enough to be sure that this is the
real issue.
If you're interested in looking and/or investigating anyway, please feel
free to check out and play with the (ice-9 debugger breakpoints
range)
module.
The other kind of breakpoint that we'd like to have is watchpoints, but this hasn't been implemented at all yet. Watchpoints may turn out to be impractical for performance reasons.