gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: GCL debug loop is broken


From: Camm Maguire
Subject: [Gcl-devel] Re: GCL debug loop is broken
Date: Thu, 05 Feb 2009 13:01:42 -0500
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Greetings!  I'm looking into this -- when was this built and by whom?
Any special settings?  Am rebuilding now from latest 2.6.8pre to
investigate.  I suggest keeping parallel installs with and without
debugging.  Suggested naming/versioning conventions most appreciated. 

Take care,

Matt Kaufmann <address@hidden> writes:

> Hi --
>
> Interrupts are broken in a local GCL 2.6.7 build.  Here I issued a
> control-C at the first prompt, and as you can see I then couldn't get
> back to the top level.
>
>   sundance:~> /lusr/bin/gcl
>   GCL (GNU Common Lisp)  2.6.7 CLtL1    Nov  5 2008 16:23:07
>   Source License: LGPL(gcl,gmp), GPL(unexec,bfd)
>   Binary License:  GPL due to GPL'ed components: (BFD UNEXEC)
>   Modifications of this banner must retain notice of a compatible license
>   Dedicated to the memory of W. Schelter
>
>   Use (help) to get some basic information on how to use GCL.
>
>   >
>   Error: Console interrupt.
>   Fast links are on: do (si::use-fast-links nil) for debugging
>   Error signalled by READ.
>   Broken at SYSTEM:TERMINAL-INTERRUPT.
>   >>>:q
>
>   Error: The tag (NIL) is undefined.
>   Fast links are on: do (si::use-fast-links nil) for debugging
>   Error signalled by SYSTEM::BREAK-CALL.
>   Backtrace: system:universal-error-handler > system::break-call > 
> SYSTEM::BREAK-QUIT
>
>   Broken at SYSTEM:TERMINAL-INTERRUPT.
>   >>>
>
> Any suggestions?
>
> Thanks --
> -- Matt
>
>
>

-- 
Camm Maguire                                        address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah




reply via email to

[Prev in Thread] Current Thread [Next in Thread]