Re: [frogs] Help with the Guile debugger

["Trevor Daniels" <t.daniels@xxxxxxxxxxx>]

Ian

This looks much like the last patch.  If you look at lines c. 314 to
c. 630 in the patch you'll see it would remove much of Carl's recent
work on the CG (I think it was Carl's).

Did you rebase to a fresh pull of master?

However ...

I have extracted the new versions of guile-debugger.scm and
guile-debugger.ly from this patch and applied them locally by
hand.  They seem to work :) so I'll try them out more carefully and
if it all seems good I'll push them to master.  I won't attempt to
extract the corresponding changes to the CG by hand though,
so if you can prepare a correct patch for those that would be
helpful; otherwise I'll check out the documentation when I'm
more familiar with debugging and make any tweaks which seem
necessary.

Many thanks for all your work on this!

Trevor

----- Original Message ----- 
From: "Ian Hulin" <ian@xxxxxxxxxxxx>
To: "Trevor Daniels" <t.daniels@xxxxxxxxxxx>
Cc: "Patrick McCarty" <pnorcks@xxxxxxxxx>; <frogs@xxxxxxxxxxx>
Sent: Friday, January 08, 2010 2:38 PM
Subject: Re: [frogs] Help with the Guile debugger


> Hi Trevor,
> On 08/01/10 00:38, Trevor Daniels wrote:
> > Ian
> >
> > Thanks, but I can't apply this as it would remove many recent 
> > changes
> > to the CG.  Could you please rebase your branch onto a fresh git
> > pull of master and make a new patch for me.
> >
> > Trevor
>
> Attached is a patch after a rebase.
>
> Cheers,
>
> Ian
>
>
> > ----- Original Message ----- From: "Ian Hulin" <ian@xxxxxxxxxxxx>
> > To: "Trevor Daniels" <t.daniels@xxxxxxxxxxx>
> > Cc: "Patrick McCarty" <pnorcks@xxxxxxxxx>; <frogs@xxxxxxxxxxx>
> > Sent: Friday, January 08, 2010 12:14 AM
> > Subject: Re: [frogs] Help with the Guile debugger
> >
> >
> > > 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
> >
> >
> >
> > ______________________________________________        This email 
> > has
> > been scanned by Netintelligence
> > http://www.netintelligence.com/email



---
----
Join the Frogs!