I'm running a kind of application server as a computational backend for our web services on a 8-processor solaris sparc machine. This server is implemented in common lisp, and uses CMUCL, listening to a socket, using the normal trick of forking a process to do the actual service.
The problem is that when I get some type-errors, the condition don't give me a description of the problem or a stack trace, but just gives segmentation fault. I don't specify the safity level explicitly, either to more or less safe than default (or the optimization for that sake), but the code is compiled. On Linux I get a sensible error message. With type errors i mean things like (say) adding a string to a number or calling a function with the wrong numbers of parameters or other stupid mistakes you can do during software development. This makes debugging hard. Is this a known problem/limitation on Solaris? -- Gisle S�lensminde Computational biology unit, University of Bergen, Norway Email: [EMAIL PROTECTED]
