Carlos Pita writes:
> Thank you very much, Dave!
>
>> Couldn't you just use (error)? It will enter the debugger if run from
>
> I'm doing exactly that, but then there is the limitation that this
> would be postmortem debugging and sometimes I want to suspend
> execution, examine the environment,
Thank you very much, Dave!
> Couldn't you just use (error)? It will enter the debugger if run from
I'm doing exactly that, but then there is the limitation that this
would be postmortem debugging and sometimes I want to suspend
execution, examine the environment, and *resume* execution.
Cheers
"Thompson, David" writes:
> On Tue, Sep 2, 2014 at 3:03 PM, Carlos Pita wrote:
>> Hi all, although I have some experience with lisps, I'm still new to
>> guile and I'm having some trouble figuring out how to invoke the
>> interactive debugger at some arbitrary point in my code. Something like:
>
On Tue, Sep 2, 2014 at 3:20 PM, Thompson, David
wrote:
> On Tue, Sep 2, 2014 at 3:03 PM, Carlos Pita wrote:
>> Hi all, although I have some experience with lisps, I'm still new to
>> guile and I'm having some trouble figuring out how to invoke the
>> interactive debugger at some arbitrary point i
On Tue, Sep 2, 2014 at 3:03 PM, Carlos Pita wrote:
> Hi all, although I have some experience with lisps, I'm still new to
> guile and I'm having some trouble figuring out how to invoke the
> interactive debugger at some arbitrary point in my code. Something like:
>
> ; code here
>
Hi all, although I have some experience with lisps, I'm still new to
guile and I'm having some trouble figuring out how to invoke the
interactive debugger at some arbitrary point in my code. Something like:
; code here
(debug)
; more code here
The closer solution I could f
