[erlang-questions] try to find the crash report (a challenge)

Ahmed Omar <>
Fri Dec 2 11:03:28 CET 2011


Well, there won't be crash report anywhere because inets does catch the
exception in httpd_resonse.erl

On Thu, Dec 1, 2011 at 2:36 PM, Joel Reymont <> wrote:

> You can get the crash reports in /tmp/error.log (in my case).
>
> This works if the list of httpd modules is set to [mod_log, mod_crash].
>
> There's still nothing shown via regular SASL channels.
>
> On Dec 1, 2011, at 1:34 PM, Yurii Rashkovskii wrote:
>
> > The problem is in httpd. httpd_request_handler has this:
> >
> >     PROCESSED = (catch Module:Function([Data | Args])),
> >
> > so it will swallow your crash. Besides, the case statement right after
> that seems to be fairly wrong. It has an all-catch clause NewMFA, and it
> assumes PROCESSED is a new MFA if it is nothing that matched before. That
> means, an EXIT tuple will be treated as a new MFA. Unless I'm missing
> something, this is just wrong.
>
> --------------------------------------------------------------------------
> - for hire: mac osx device driver ninja, kernel extensions and usb drivers
> ---------------------+------------+---------------------------------------
> http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
> ---------------------+------------+---------------------------------------
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>



-- 
Best Regards,
- Ahmed Omar
http://nl.linkedin.com/in/adiaa
Follow me on twitter
@spawn_think <http://twitter.com/#!/spawn_think>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111202/6b9e189e/attachment.html>


More information about the erlang-questions mailing list