perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Hay <>
Subject Re: New Windows mod_perl binaries available
Date Tue, 30 Apr 2013 00:45:13 GMT
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 <> wrote:
> Hi Issac,
> On Mon, Apr 29, 2013 at 4:08 PM, Issac Goldstand <> 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

View raw message