Hi! Andy Wingo <wi...@pobox.com> writes:
> Tracepoints and breakpoints are "traps", which can enabled and disabled > and listed with the "enable", "disable", "delete", and "traps" REPL > meta-commands. > > I can also break at source locations now: > > scheme@(guile-user)> ,break-at-source "ice-9/boot-9.scm" 2242 > Trap 2: Breakpoint at ice-9/boot-9.scm:2242. > scheme@(guile-user)> (resolve-module '(ice-9 popen)) > Trap 0: (#<procedure b038e0 at ice-9/boot-9.scm:2234:4 (name > #:optional...> #) > Trap 2: Breakpoint at ice-9/boot-9.scm:2242 > Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue. > scheme@(guile-user) [1]> ,bt > In ice-9/boot-9.scm: > 2242:14 0 (#<procedure b038e0 at ice-9/boot-9.scm:2234:4 (na...> ...) > scheme@(guile-user) [1]> ,q > Trap 0: #<directory (ice-9 popen) 12d8bd0> > $2 = #<directory (ice-9 popen) 12d8bd0> > > Here we see that tracepoints and breakpoints interoperate well. Woow, excellent! :-) Ludo’.
