Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of steve.m.hay@googlemail.com
 designates 209.85.214.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABD0r12tGtXVjwLJUKE49ZftdY3UvqzS=yPY_3aDYYzKv9b2Sw@mail.gmail.com>
References: 
 <CADED=K68BV8MK8Ezt+vL2z4wSHtkRfYog6uAX7aOu6+joiFe8w@mail.gmail.com>
	<CABD0r11z_9CXM926BS75aZeohNXPo1p2vwcZC0uw4qHu0jOc2Q@mail.gmail.com>
	<517E5149.80101@beamartyr.net>
	<CABD0r134faPdqn83yWa8S-K3CHp__O5dSEuQK7hc6=JGJv1ejA@mail.gmail.com>
	<517E7EF5.1090506@beamartyr.net>
	<CABD0r12tGtXVjwLJUKE49ZftdY3UvqzS=yPY_3aDYYzKv9b2Sw@mail.gmail.com>
Date: Tue, 30 Apr 2013 01:45:13 +0100
Message-ID: 
 <CADED=K5N_9eMACkUNKWA6Eo+0i360KPe2HL8q-KF7f1SZR8Q7w@mail.gmail.com>
Subject: Re: New Windows mod_perl binaries available
From: Steve Hay <steve.m.hay@googlemail.com>
To: Michiel Beijen <michiel.beijen@otrs.com>
Cc: Issac Goldstand <margol@beamartyr.net>,
 mod_perl list <modperl@perl.apache.org>
Content-Type: text/plain; charset=UTF-8

Do you have an exception-trap at the highest level around your
program? I always have the entire program enclosed within a try-catch
block (using Try::Tiny; even just an eval {} would be better than
nothing), so if any Perl-level exceptions are thrown then they get
caught and logged. It won't trap C-level blow-ups (crashes), though,
but it might help, depending on the problem.

I may have a go at building debug binaries sometime, but you'd also
need debug perl and httpd for the full details. (I've only done
complete debug builds of everything before, not just mod_perl
components for, say, StrawberryPerl...) Which perl/httpd are you using
(where from, and what versions)?

Do you have cut-down sample programs which you can post for others to
reproduce your problem with?

On 29 April 2013 15:15, Michiel Beijen <michiel.beijen@otrs.com> wrote:
> Hi Issac,
>
> On Mon, Apr 29, 2013 at 4:08 PM, Issac Goldstand <margol@beamartyr.net> wrote:
>> First of all, see if you can get a stacktrace.
>
> so how would you recommend I create a stack trace? This has been my
> whole problem, the process simply restarts and I don't see why.
>
>> There's also always spreading print/debug statements around - I'm
>> unfortunately not so up-to-date on the various perl profiling modules
>> around, but they might be helpful.
>
> This is not possible here as I can reproduce it sending X number of
> requests to my app. This can be *any* request to *any* part so I have
> no chance to find the appropriate part of the app or any of the CPAN
> modules it uses. This is why I'm looking for a way to generate some
> kind of debug output so I know at least *what* the application does
> before it exits.
> --
> Mike