Yeah, the root cause seems to some error which, in trying to report causes another error.
Maybe you can hack up (LABELS HUNCHENTOOT::REPORT-ERROR-TO-CLIENT :IN HUNCHENTOOT::PROCESS-REQUEST) to show the type of each argument so that you can at least see what error it might have been trying to print. That's not foolproof because if the obsolete dynamic-extent object already reached there, there's no guarantee that you're not already looking at scrambled bits. However if the arguments themselves are reasonable but merely contain some other dynamic-extent object, you might be in a better position to think about what it might have wanted to print.
Yeah, the root cause seems to some error which, in trying to report causes another error. :REPORT- ERROR-TO- CLIENT :IN HUNCHENTOOT: :PROCESS- REQUEST) to show the type of each argument so that you can at least see what error it might have been trying to print. That's not foolproof because if the obsolete dynamic-extent object already reached there, there's no guarantee that you're not already looking at scrambled bits. However if the arguments themselves are reasonable but merely contain some other dynamic-extent object, you might be in a better position to think about what it might have wanted to print.
Maybe you can hack up (LABELS HUNCHENTOOT: