(Moved to sbcl-help from sbcl-devel.)
On Fri, 27 May 2005, Robert Marlow wrote:
> Please, I'd appreciate it if everyone who has any suspicion at all of
> what causes this bug please investigate it and help fix it. I can't
Have you tried the couple of as-of-yet-unmerged threading patches by Gabor
Melis? (Cannot remember which ones they are offhand, but comparing
sbcl-devel archives with history of version.lisp-expr should pinpoint them
with reasonable effort.) Did that change anything?
Have you been able to reduce the test case in case of your server
application by eg. binary section? With sight unseen code it is anybodys
guess where the problem lies.
Can you write the server using serve-event or forking-style instead, or
possibly checkpointing live data to disk regularly, and keeping a watchdog
process to kill & restart after craches?
I'm afraid that I can't be of more help vis-a-vis threading as I don't
currently have access to any linux boxes.
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."
From: Robert Marlow <bobstopper@bo...> - 2005-05-28 02:35:35
Someone else pointed out my original post appeared negative toward sbcl
developers. Sorry about that. I definitely harbour no negative feelings
toward sbcl developers. You guys are doing great work and SBCL rocks my
world. I was just being much more whingy than necessary because I was in
panic mode. So Dan and any other developers, I apologise if it seemed my
negativity was directed toward you in any way.
And I'm sorry I posted to sbcl-devel instead of sbcl-help. I wasn't
Now, with those apologies out of the way, all I'm really asking for is a
nice consise list of known issues with SBCL threads, their nature,
possible fixes etc etc so I have somewhere to start looking. I know I'm
probably dreaming else I'd have found it by now, but whatever you guys
use for bugtracking would be all I need if it's publically accessible in
any way. I'm kinda hoping there's something I can use other than the
sbcl-devel archives with more info than the BUGS file.
(Right now what I've been doing is google for thread related bugs on the
mailing list, give up because the word "thread" appears in every email
on the web, ask a developer whether symptoms I'm experiencing are due to
a known bug, ask a developer what's known about the bug and ask a
developer if there's any known fix. Given Dan's the threads guy he tends
to be that developer a lot so I'm probably getting up his nose (Sorry
Dan!). So if there's any simple way I can find this information directly
that'd be great. If not, oh well.)
Robert Marlow <bobstopper@...>