> > 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. > > When this happens, SBCL refuses to continue and drops into LDB. I had to > disable LDB so that the application can be automatically restarted. > > have seen something like this (dropping into the ldb) but I think it was related to mutexes and sb-ext:schedule-timer and/or heap exhaustion while reading xml prevalence logs.
Also I had one case with a misplaced delimited continuation which did cause this. sorry I don't remember more .. -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
