cl-repl binaries cause fatal error if the user entered expressions cause an error

[digikar99]

This occurs right from v0.6.5 to v0.7.0.

  ___  __          ____  ____  ____  __
 / __)(  )    ___ (  _ \(  __)(  _ \(  )
( (__ / (_/\ (___) )   / ) _)  ) __// (_/\
 \___)\____/      (__\_)(____)(__)  \____/
cl-repl 0.6.5 on SBCL 2.1.11.debian
(C) 2017-2018 TANI Kojiro <kojiro0531@gmail.com>

CL-USER> a
The variable A is unbound.
 [Condition of type UNBOUND-VARIABLE]

Restarts:
 0: [CONTINUE] Retry using A.
 1: [USE-VALUE] Use specified value.
 2: [STORE-VALUE] Set specified value and use it.
 3: [*ABORT] Deduce debugger level.
 4: [*EXIT] Exit CL-REPL.
 5: [*RETRY] Try evaluating again.

Backtrace:
 0: (SB-INT:SIMPLE-EVAL-IN-LEXENV A #<NULL-LEXENV>)
 1: (EVAL A)
 --more--

Usage:
  Ctrl+r: select restart. Ctrl+t: show backtrace.

CORRUPTION WARNING in SBCL pid 104802 tid 104802:
Memory fault at 0x559e95ff4410 (pc=0x7455cfd4a70f, fp=(nil), sp=0x7455cffae588) tid 104802
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
Unhandled memory fault at #x559E95FF4410.
 [Condition of type MEMORY-FAULT-ERROR]

Restarts:
 0: [*ABORT] Deduce debugger level.
 1: [*EXIT] Exit CL-REPL.
 2: [*RETRY] Try evaluating again.

Backtrace:
 0: (SB-SYS:MEMORY-FAULT-ERROR #<unused argument> #.(SB-SYS:INT-SAP #X559E95FF4410))
 1: ("foreign function: call_into_lisp")
 --more--

Usage:
  Ctrl+r: select restart. Ctrl+t: show backtrace.

;; These error nesting continues about 8 times

fatal error encountered in SBCL pid 104802 tid 104802:
maximum interrupt nesting depth (8) exceeded

Welcome to LDB, a low-level debugger for the Lisp runtime environment.