Re: Interactive Debugging

[Christopher Lam <christopher.lck@gmail.com>]

Agree it'll be a major aid to decreasing the learning curve. For now the
only way to analyse a variable in a script is to (pk) it, which is annoying
when it's a record/alist etc. Need to refine the pk several times or write
a custom printer.

Not sure how much knowledge of debugger is required, all I want to do is to
dump local variables at the breakpoint.

On Sat, 19 Oct 2019, 05:23 Mark H Weaver, <mhw@netris.org> wrote:

> "Thompson, David" <dthompson2@worcester.edu> writes:
>
> > On Fri, Oct 18, 2019 at 8:40 AM Matt Wette <matt.wette@gmail.com> wrote:
> >>
> >> On 10/17/19 9:39 PM, Christopher Howard wrote:
> >> > Hi, it seems like with the flexibility of Guile, I should be able to
> do
> >> > something like this:
> >> > ```(define (foo)  (let ((a 1)        (b 2)        (c 3))
> (jump-into-
> >> > debugging-repl)))```
> >> > And have access to a, b, and c and their values. But I'm not quite
> >> > figuring out how to this.
> >> >
> >>
> >> Define dump-into-debugging-repl as
> >>
> >> (start-repl #:debug (make-debug (stack->vector (make-stack #t)) 0
> >> "trap!" #t))
> >
> > I think something like this should be shipped in the (system repl
> > debug) module.  I'm used to quick and easy access to a debugger in
> > other languages, such as Ruby, and having to wrap your head around the
> > REPL, debug, and stack code is too much to ask of any new Guiler.
>
> For what it's worth, I think something like this would be a welcome
> addition.  However, my knowledge of the Guile debugger is currently
> quite weak, so I'd prefer to hear from Andy before proceeding.
>
>      Thanks,
>        Mark
>
>