Re: [Erlyaws-list] crash in yaws code leaves connection hanging

[Claes W. <kl...@ta...>]

Michael Radford wrote:

>   Error in process <0.9696.0> on node 'my_node' with exit value: {function_clause,[{lists,foldl,[#Fun<yaws_server.48.125267158>,{["foo"],{[],[]}},{some_tuple, ...}]},{yaws_server,vdirpath,3},{yaws_server,mappath,3},{yaws_cgi,cgi_env...
> 
> So, yes, it seems to be a bug that I passed #arg.opaque as a tuple
> instead of a list (opaque is not very opaque after all...but
> that's another discussion).

Agreed, there's some cruft in the opaque field e.g. vdir specifications
are there when they really should be a proper field in #sconf{}

> 
> The disturbing part is that the client connection is not closed
> when the crash occurs.

Bad

> 
> Is there an easy fix to ensure that crashes within yaws itself are
> detected and handled as nicely as crashes within user appmods or
> auto-generated modeuls from .yaws files?

Hmmm this needs to be debugged - I'll have a look at it. Thanks
for reporting.

Client socket should definitely die here.

/klacke