Hi again,
Maybe the problem I reported in my last message
is only xmaxima related.
xmaxima on my laptop not only produces warnings
on the shell from which it is started if I use that
shel, but it also produces warnings upon being ended.
My setting is: Ubuntu 6.06, Maxima 5.11.99rc2 + sbcl.
The warnings begin with:
"
caruso at Pentium-IV:~$ xmaxima &
[1] 32246
caruso at Pentium-IV:~$ Maxima 5.11.99rc2 http://maxima.sourceforge.net
Using Lisp SBCL 0.9.8
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
This is a development version of Maxima. The function bug_report()
provides bug reporting information.
(%i1) jfa: starting server on port 4008
Help! 11 nested errors. SB-KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.
0: (BACKTRACE 536870911 #<SYNONYM-STREAM :SYMBOL SB-SYS:*TTY* {961B969}>)
1: ((LAMBDA NIL))
2: ((LAMBDA NIL))
3: (SB-IMPL::%WITH-STANDARD-IO-SYNTAX #<CLOSURE (LAMBDA NIL) {961BA85}>)
4: (SB-IMPL::ERROR-ERROR)
5: (SB-IMPL::INFINITE-ERROR-PROTECTOR)
6: (ERROR "SIGPIPE at #X~X")
7: ((FLET #:G178))
8: (SB-UNIX::SIGPIPE-HANDLER #<unavailable argument> #<unavailable
argument> #.(SB-SYS:INT-SAP #XB7C3A1AC))
9: (SB-SYS:INVOKE-INTERRUPTION #<CLOSURE (LAMBDA NIL) {961B19D}>)
10: ("foreign function: call_into_lisp")
11: ("foreign function: funcall3")
12: ("foreign function: interrupt_handle_now")
.............................
"
and end with:
"
.............................
108: ("bogus stack frame")
109: (SB-IMPL::FROB-OUTPUT #<SB-SYS:FD-STREAM for "a constant string"
{9614DC1}> #.(SB-SYS:INT-SAP #XB7A39000) 0 18 T)
110: (SB-IMPL::FLUSH-OUTPUT-BUFFER #<SB-SYS:FD-STREAM for "a constant
string" {9614DC1}>)
111: (FORCE-OUTPUT #<SB-SYS:FD-STREAM for "a constant string" {9614DC1}>)
112: (SB-INT:FLUSH-STANDARD-OUTPUT-STREAMS)
113: (INVOKE-DEBUGGER #<SIMPLE-ERROR {96191C9}>)
fatal error encountered in SBCL pid 32251(tid 3085452976):
%PRIMITIVE HALT called; the party is over.
The system is too badly corrupted or confused to continue at the Lisp
level. If the system had been compiled with the SB-LDB feature, we'd drop
into the LDB low-level debugger now. But there's no LDB in this build, so
we can't really do anything but just exit, sorry.
"
Fabrizio