On Wed, 13 Mar 2019 08:51:04 -0700 Hermann Calabria <hermann@ivouch.com> wrote:
I don’t have fatal warnings turned on.
Also, reviewing the stack trace, none of the calls appear to go through the app. The only packages involved are:
HTTP::Server::Simple Dancer::Handler::Standalone Dancer::Handler Dancer
Here are lines 396 and 397 of HTTP/Server/Simple.pm (version 0.52): my $remote_sockaddr = getpeername( $self->stdio_handle ); my $family = sockaddr_family($remote_sockaddr); So $remote_sockaddr is undef. It should avoid calling sockaddr_family() in that case.
From: Andrew Beverley Sent: Tuesday, March 12, 2019 3:56 PM To: Perl Dancer users mailing list Cc: Hermann Calabria Subject: Re: [dancer-users] Dancer crashing
On Tue, 12 Mar 2019 15:08:46 -0700 Hermann Calabria wrote:
Sure, it’s probably something my app is doing. However I expect Dancer to be resilient enough to not crash in this manner.
FWIW, I did notice that the crash appeared to happen because of an uninitialized value. Do you have fatal warnings turned on, and could that be one of the causes? I don't know, but does Dancer normally run without fatal warnings, and maybe the problem you encountered wouldn't normally be fatal?
Andy
-- C. Chad Wallace, B.Sc. The Lodging Company http://www.lodgingcompany.com/ OpenPGP Public Key ID: 0x262208A0 +1 250-869-4931 ext. 6251