[hunchentoot-devel] Hard to catch errors below process-request

[Hans Hübner]

On Thu, Jan 20, 2011 at 10:20 PM, AVS <lispercat at gmail.com> wrote:
> The issue is this: If any of the functions fail when called from
> start-output, you'll receive an empty response and the debugger will
> not catch which function caused the error.
> I described in the previous message that in my case (string-to-octets
> ..) failed. The failure may depend on your input.
> I just said that to reproduce that scenario (silent error without
> debugger being invoked) just put any failing function inside
> start-output and issue a page request from the browser.
> You'll receive an empty page and no debugger will be signaled.
> Maybe it's a normal scenario, but it's hard to find the failing
> function in this case.

I'm just trying to find out how pressing the problem is - Is it
something that a user or an application developer may run into, or is
it something that just happens when you poke around in the source code
and break it in unexpected ways?  From quickly glancing at
start-output, I see no calls back into user code, but you have run
into it nevertheless.  How, why?

-Hans