Causing an exception rather than calling the debugger

Blake McBride blake at
Mon Apr 30 23:11:34 UTC 2018


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.


Blake McBride
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the armedbear-devel mailing list