Re: Causing an exception rather than calling the debugger

Hi Blake,

I, too, have some Lisp code embedded in Java code. I investigated this
issue in the following three posts beneath:
https://mailman.common-lisp.net/pipermail/armedbear-devel
titled, "disabling debugger in production"

/2016-June/003690.html
/2016-July/003692.html
/2017-April/003837.html

My current solution is to call the installDebuggerHook() function
described in the first post. And also to install the error() function as
described at the bottom of the last post. But as that post says, this
solution isn't perfect.

Vibhu