From: Martin Rubey on
(sorry, that's probably not quite the right place to post, excuse me
please...)

I just installed sbcl-1.0.36 on a 64 bit machine, and noticed that
Ctrl-c doesn't interrupt computations that take too long for my
patience. Is there any workaround for this?

Many thanks,

Martin
From: Tamas K Papp on
On Mon, 08 Mar 2010 12:34:56 +0100, Martin Rubey wrote:

> (sorry, that's probably not quite the right place to post, excuse me
> please...)
>
> I just installed sbcl-1.0.36 on a 64 bit machine, and noticed that
> Ctrl-c doesn't interrupt computations that take too long for my
> patience. Is there any workaround for this?
>
> Many thanks,
>
> Martin

It works for me (64 bit, same version, command line, see output below).
Are you using it inside Emacs/SLIME or some kind of wrapper library?

Tamas


This is SBCL 1.0.36, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
; loading system definition from
; /usr/local/lib/sbcl/sb-bsd-sockets/sb-bsd-sockets.asd into #<PACKAGE
"ASDF0">
; registering #<SYSTEM SB-BSD-SOCKETS {10033874E1}> as SB-BSD-SOCKETS
; registering #<SYSTEM SB-BSD-SOCKETS-TESTS {1002C6A071}> as
; SB-BSD-SOCKETS-TESTS
; loading system definition from /usr/local/lib/sbcl/sb-posix/sb-
posix.asd into
; #<PACKAGE "ASDF0">
; registering #<SYSTEM SB-POSIX {100307ACD1}> as SB-POSIX
; registering #<SYSTEM SB-POSIX-TESTS {100329D031}> as SB-POSIX-TESTS
* (tagbody top (go top)) ;; and I press Ctrl-C

debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD
"initial
thread" RUNNING

{10036E3751}>:
Interactive interrupt at #x10033F1C70.

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE] Return from SB-UNIX:SIGINT.
1: [ABORT ] Exit debugger, returning to top level.

((LAMBDA ()))
0]
From: Martin Rubey on
Tamas K Papp <tkpapp(a)gmail.com> writes:

> On Mon, 08 Mar 2010 12:34:56 +0100, Martin Rubey wrote:
>
>> (sorry, that's probably not quite the right place to post, excuse me
>> please...)
>>
>> I just installed sbcl-1.0.36 on a 64 bit machine, and noticed that
>> Ctrl-c doesn't interrupt computations that take too long for my
>> patience. Is there any workaround for this?
>>
>> Many thanks,
>>
>> Martin
>
> It works for me (64 bit, same version, command line, see output below).

Oh, sorry, that means the problem is elsewhere (I did try it on the
command line, but my test was not good, obviously)

> Are you using it inside Emacs/SLIME or some kind of wrapper library?

Yes, I built FriCAS (a computer algebra system, cc-ing to that list)
with it. I checked:

martin(a)bustopherjones:~$ fricas
Checking for foreign routines
AXIOM="/home/martin//lib/fricas/target/x86_64-unknown-linux"
spad-lib="/home/martin//lib/fricas/target/x86_64-unknown-linux/lib/libspad.so"
foreign routines found
openServer result 0
FriCAS (AXIOM fork) Computer Algebra System
Version: FriCAS 2010-01-08
Timestamp: Friday March 5, 2010 at 12:34:46
-----------------------------------------------------------------------------
Issue )copyright to view copyright notices.
Issue )summary for a summary of useful system commands.
Issue )quit to leave FriCAS and return to shell.
-----------------------------------------------------------------------------

(1) ->
(1) -> )lisp (tagbody top (go top))

and pressing Ctrl-c doesn't "work" anymore.

Curiously, when suspending with Ctrl-z, I indeed return to the shell,
but the process keeps consuming 100% cpu!

Many thanks for clarifying the source of the trouble!

Martin