On Wed, 10 Aug 2005 13:22:22 +0100, Martin Simmons martin@lispworks.com wrote:
The debugger's idea of the args to EDITOR::DISPLAY-COMPILE-FILE-STATUS might be bogus, so the output from tracing COMPILE-FILE and EDITOR::DISPLAY-COMPILE-FILE-STATUS would be useful.
See below. This is what is written to the output pane up to the point where the error occurs.
0 COMPILE-FILE > ...
COMPILER::INPUT-FILE : #<EDITOR::EDITOR-REGION-STREAM #<EDITOR:BUFFER foo.lisp> 20683C14> COMPILER::IN-MEMORY : T :PARTIALP : T :FASL-P : NIL COMPILER::REAL-SOURCE-FILE-NAME : #P"C:/tmp/foo.lisp" :PROGRESS-HOOK : #<closure (SUBFUNCTION 1 EDITOR::PANE-PROGRESS-HOOK) 206AB25A>
;;; Safety = 3, Speed = 1, Space = 1, Float = 1, Interruptible = 0 ;;; Compilation speed = 1, Debug = 2, Fixnum safety = 3 ;;; Source level debugging is on ;;; Source file recording is on ;;; Cross referencing is on ; (TOP-LEVEL-FORM 1) ; TRANSPOSE-LISTS-EDI 0 COMPILE-FILE < ... << VALUE-0 : NIL 0 EDITOR::DISPLAY-COMPILE-FILE-STATUS > ...
EDITOR::DONE : NIL