Causing an exception rather than calling the debugger

[Blake McBride]

Hi,

I embedded ABCL in an app some years ago.  When an error occurred, ABCL
threw an exception.  It did what I want.

Today I upgraded to the latest jar and I am experiencing a different
behavior.  When an error occurs ABCL enters a debug REP loop.  Calling a
REP loop on error is perfect for interactive use but not workable in an
embedded situation.

I'm hoping there is a simple way for me to change this behavior.  Any help
is greatly appreciated.

Thanks.

Blake McBride
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/armedbear-devel/attachments/20180430/1ee4eef3/attachment.html>