From: Nick L. <nd...@ra...> - 2010-01-09 07:36:42
|
I came across this, in a raw shell on Ubuntu. Lisp says I can type "(SB-EXT:QUIT) to exit from SBCL" but doing so gives me an unpleasant slap on the wrist and no exit. OK, I know full well that I can get out of Lisp either with control-D or by aborting the break and trying (sb-ext:quit) again. But a more innocent user might not. The defect is compounded by Lisp going out of its way to suggest using (sb-ext:quit) in the first place. - nick ndl@vulture:~$ sbcl This is SBCL 1.0.32, 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. * ^C debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD "initial thread" RUNNING {A986781}>: Interactive interrupt at #xB7FE2422. 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. ("bogus stack frame") 0] (SB-EXT:QUIT) #<SB-DI::BOGUS-DEBUG-FUN "bogus stack frame"> has no debug variable information. 0] |
From: Nikodemus S. <nik...@ra...> - 2010-01-11 19:28:23
|
2010/1/9 Nick Levine <nd...@ra...>: > I came across this, in a raw shell on Ubuntu. Lisp says I can type > "(SB-EXT:QUIT) to exit from SBCL" but doing so gives me an unpleasant > slap on the wrist and no exit. > OK, I know full well that I can get out of Lisp either with control-D > or by aborting the break and trying (sb-ext:quit) again. But a more > innocent user might not. The defect is compounded by Lisp going out of > its way to suggest using (sb-ext:quit) in the first place. Do you possibly have something interesting in your .sbclrc? Works on Darwin just fine (I'll check Linux tomorrow): > sbcl --no-userinit This is SBCL 1.0.33.28, 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. * ^C debugger invoked on a SB-SYS:INTERACTIVE-INTERRUPT in thread #<THREAD "initial thread" RUNNING {1002ADAFA1}>: Interactive interrupt at #x7FFF80E22582. 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. ((FLET SB-UNIX::INTERRUPT-IT)) 0] (SB-EXT:QUIT) Cheers, -- Nikodemus |
From: Christophe R. <cs...@ca...> - 2010-01-11 20:19:24
|
Nikodemus Siivola <nik...@ra...> writes: > 2010/1/9 Nick Levine <nd...@ra...>: > >> I came across this, in a raw shell on Ubuntu. Lisp says I can type >> "(SB-EXT:QUIT) to exit from SBCL" but doing so gives me an unpleasant >> slap on the wrist and no exit. > >> OK, I know full well that I can get out of Lisp either with control-D >> or by aborting the break and trying (sb-ext:quit) again. But a more >> innocent user might not. The defect is compounded by Lisp going out of >> its way to suggest using (sb-ext:quit) in the first place. > > Do you possibly have something interesting in your .sbclrc? Works on > Darwin just fine (I'll check Linux tomorrow): I confirm Nick's symptoms: on my laptop (x86/linux, default build -- i.e. threaded :-) the debugger says ("bogus stack frame") and sb-ext:quit does not work. |
From: Nick L. <nd...@ra...> - 2010-01-11 20:08:15
|
Nikodemus, Do you possibly have something interesting in your .sbclrc? Works on Darwin just fine (I'll check Linux tomorrow): I renamed my .sbclrc and checked that this was still broken before reporting it. - n |