"Nick Dimiduk" <ndimiduk@...> writes:
> When starting sbcl (the binary download), the crash reporter pops up
> and informs me that a thread has crashed. Error message aside, the
> binary appears to function correctly. Threading is not available on
For background, google for "sbcl crash reporter".
In short, this is an OS X bug in the crash reporter, which Apple is
aware of, but not probably going to fix any time soon.
There are two workarounds:
1. the user-level workaround is to twiddle with crash reporter
settings and make it shut up when a non-GUI application receives a
SIGSEGV. (This is the default setting, that you are seeing the
reporter means that the crash reporter settings have been altered.)
2. the implementation (SBCL) level workaround is to use Mach
exception handlers instead of the posix ones. This will probably
happen sooner or later, but I'm not aware of anyone working on
it right now -- so it may happen next week or it may happen just
before Apple fixes crash reporter...
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."