Buildapp's dumper script currently sets sb-ext:*invoke-debugger-hook* to NIL as one of its final steps. The intent is that user code should initialize the value at application startup. However, SBCL can fail and enter the debugger before any of the init hooks or custom toplevel functions are called.
One strategy to avoid this problem is to wrap all loading operations in a form that binds *invoke-dynamic-hook*, and checks to see whether it's modified as a result of the load, and then saves that modified value at the end of the dumper script.
Buildapp's dumper script currently sets
sb-ext:*invoke-debugger-hook*
to NIL as one of its final steps. The intent is that user code should initialize the value at application startup. However, SBCL can fail and enter the debugger before any of the init hooks or custom toplevel functions are called.One strategy to avoid this problem is to wrap all loading operations in a form that binds
*invoke-dynamic-hook*
, and checks to see whether it's modified as a result of the load, and then saves that modified value at the end of the dumper script.