I recall some time ago, the break and backtrace capability of
Hunchentoot was removed, perhaps to make it less platform dependent.
But I still find myself often trying to find the origin of cryptic
error messages, and adding FORMAT and BREAK statements to narrow down
the problem area. What is a good way to drop in support for, say,
SBCL, so that an error will break into the debugger with a backtrace,
or even dump the backtrace to the log file?
--
Jonathon McKitrick