Re: [frogs] Help with the Guile debugger

[Ian Hulin <ian@xxxxxxxxxxxx>]

This is a multi-part message in MIME format.

Hi Trevor,

On 07/01/10 23:55, Trevor Daniels wrote:
> Patrick McCarty wrote Thursday, January 07, 2010 7:10 PM
>
>
> > At the prompt, if I manually invoke "(use-modules (scm
> > guile-debugger))", then the bindings (set-break!, etc.) become
> > visible.
>
> This seems to be a viable way to debug Scheme code.  I'd be happy
> to amend the CG to say this, but there may be more problems.
> If I set a break-point and enter (quit) the debugger is entered at the
> break-point as it should be.  All the debug commands seem to work
> fine, except for finish.  This produces the error:
>
> Internal debugger error:
> usr/share/guile/1.8/ice-9/debugger/command-loop.scm:51:6:
> In procedure throw in expression (apply throw key ...):
> usr/share/guile/1.8/ice-9/debugger/command-loop.scm:51:6:
> Unbound variable: trace-trap
work-round - use quit or continue at the debug> prompt instead.
> Not sure if this is relevant or due to my lack of familiarity with
> the guile debugger.
>
> > Somehow `lilypond-module' needs to remember that it is using the
> > guile-debugger module *before* `top-repl' is invoked.
>
> This would be better if you can figure out a way to do it.

Attached patch should do this.

Cheers,
Ian