[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: saving and restoring the error stack trace
From: |
Neil Jerram |
Subject: |
Re: saving and restoring the error stack trace |
Date: |
Fri, 01 Sep 2006 08:34:00 +0100 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) |
<address@hidden> writes:
> ---- Neil Jerram <address@hidden> wrote:
>
>> 5.21.2 Debugging when an error occurs
>
> ...
>
> Thank you, thank you! This bit of documentation has been sorely
> needed for a long time.
That's true. Over the last few years it's a question that has been
regularly asked on the mailing lists, and never quite definitively
answered.
> Many people come to Guile from the "C side"
> with poor or nonexistant Scheme experience. Usually to add Guile to
> some C application, which of course throws out the REPL and it's
> backtracing and error reporting capabilities. So then when errors
> happen you have no idea where or how. Making a C program extended
> by Guile spit out a proper backtrace is a twisty maze of handlers
> and catchers, and some of them need to be lazy. (Lazy? Why would I
> want a *lazy* handler, I want a hard-working, full-featured kind of
> handler, not some wimpy light weight *lazy* handler!)
:-)
> My point is that getting good backtraces from C is non-obvious and a
> huge hindrance to people just learning how to use Guile and Scheme.
> But that's over now. Thanks again Neil.
Thanks for your kind words.
Regards,
Neil
Re: saving and restoring the error stack trace, Volkan YAZICI, 2006/09/07