backtrace on compilation-time errors

ID	Created	Type	mocl Version	Dev OS	Target	Status
#31	by informatimago on 2013-11-25 (1644 days ago)	enhancement	n/a	n/a	n/a	open
Description
Summary:

Since Lisp is a #1=(programming . #1#) language, lisp code is executed at compilation-time.

Given the restrictions on mocl repl, it would be important to provide better debugging information upon compilation-time errors.


Steps to Reproduce:

Compile some file with a compilation-time error.

Expected Results:

An error report with at least a full stack dump.

Actual Results:

An insufficient "Control stack exhausted".


    -*- mode: compilation; default-directory: "~/src-lisp/mocl/mocl-example-lisp-contacts-android/" -*-
    Compilation started at Mon Nov 25 00:29:01

    make -C ~/src-lisp/mocl/  android
    make: Entering directory `/home/pjb/src-lisp/mocl'
    unset LC_ALL;unset LC_MONETARY;unset LC_NUMERIC;unset LC_MESSAGES;unset LC_COLLATE;unset LC_TIME;export LC_CTYPE=en_US.utf-8;export LANG=C ; cd mocl-example-lisp-contacts-android ; mocl --android LispContacts app.lisp
    (source-form.lisp:1384) Warning: Compile-time evaluation failed at RT::THROW.
    INFO: Control stack guard page unprotected
    Control stack guard page temporarily disabled: proceed with caution
    (list.lisp:204) Warning: Control stack exhausted (no more space for function call frames).
    This is probably due to heavily nested or infinitely recursive function
    calls, or a tail call that SBCL cannot or has not optimized away.

    PROCEED WITH CAUTION.
    Unhandled error: Control stack exhausted (no more space for function call frames).
    This is probably due to heavily nested or infinitely recursive function
    calls, or a tail call that SBCL cannot or has not optimized away.

    PROCEED WITH CAUTION.
    Quitting.
    ; 
    ; compilation unit aborted
    ;   caught 1 fatal ERROR condition
    make: *** [mocl-example-lisp-contacts-android/LispContacts/jni/mocl/program.c] Error 1
    make: Leaving directory `/home/pjb/src-lisp/mocl'

    Compilation exited abnormally with code 2 at Mon Nov 25 00:29:02


Notes:
Comments

(no comments)