so, just when I managed to squash one persistent failure (running out of threads due to sb-ext:run-process not returning), I seem to have awoken another. I've got two, possibly unrelated, issues. First, the more benign one:
I see the following message quite often in the logs:
[2008-12-23 18:47:38 [ERROR]] Error while processing connection: The value 1058 is not of type
(MOD 1025). occasionally the message is:
[2008-12-23 18:46:06 [ERROR]] Error while processing connection: The value 1065 is not of type
(UNSIGNED-BYTE
10).
any idea where these might be coming from?
The second, more serious, problem is that I seem to end up in ldb after a few days of usage:
* Argh! corrupted error depth, halting fatal error encountered in SBCL pid 60417(tid 134658560): %PRIMITIVE HALT called; the party is over.
Welcome to LDB, a low-level debugger for the Lisp runtime environment. ldb> Argh! corrupted error depth, halting fatal error encountered in SBCL pid 60417(tid 134659072): %PRIMITIVE HALT called; the party is over.
Welcome to LDB, a low-level debugger for the Lisp runtime environment. ldb> Argh! corrupted error depth, halting fatal error encountered in SBCL pid 60417(tid 136982272): %PRIMITIVE HALT called; the party is over.
Welcome to LDB, a low-level debugger for the Lisp runtime environment. ldb> >
This is a fairly unhelpful error, but I'm wondering if the above- mentioned error isn't tickling some bug in the sbcl/freebsd error handling code. This ldb droppage is fairly new, AFAICT. There have certainly been other failure modes, but this one is new and I'm wondering if might be due to recent changes in either SBCL or hunchentoot. In any event, I'll try to get some more info from ldb to see if I can track this down.
Cyrus