I only get the error with SBCL 1.3.18 and the backtrace I get is not really useful. Mayby okflo could send more precise information to cl+ssl ? They have modified code on master about this part of cl+ssl but I get the "same" (?) error with this version.
Thank you okflo. I don't know why I dont't get the whole backtrace here...
I just posted a bug on cl+ssl tracker : https:/ /github. com/cl- plus-ssl/ cl-plus- ssl/issues/ 48
I only get the error with SBCL 1.3.18 and the backtrace I get is not really useful. Mayby okflo could send more precise information to cl+ssl ? They have modified code on master about this part of cl+ssl but I get the "same" (?) error with this version.