get backtrace emailed when code dies running under ModPerl::RegistryPrefork?

2009-03-02 Thread Matthew Lenz
As I've mentioned in previous posts, I'm migrating from an older environment to a new environment with mod_perl 2. With mod_perl 1.x we had VERY OLD customised version of CGI::Carp (with fatalsToBrowser) printing an error to the browser AND sending an email with backtrace and environment

Re: get backtrace emailed when code dies running under ModPerl::RegistryPrefork?

2009-03-02 Thread Perrin Harkins
On Mon, Mar 2, 2009 at 9:54 AM, Matthew Lenz matt...@nocturnal.org wrote: According to the docs CGI::Carp doesn't function properly with fatalToBrowser under mod_perl 2. I'm not sure if that's accurate or not, but setting a $SIG{__DIE__} handler should work fine. BTW, I assume you mean

Re: get backtrace emailed when code dies running under ModPerl::RegistryPrefork?

2009-03-02 Thread Matthew Lenz
On Mon, 2009-03-02 at 10:20 -0500, Perrin Harkins wrote: On Mon, Mar 2, 2009 at 9:54 AM, Matthew Lenz matt...@nocturnal.org wrote: According to the docs CGI::Carp doesn't function properly with fatalToBrowser under mod_perl 2. I'm not sure if that's accurate or not, but setting a

Re: get backtrace emailed when code dies running under ModPerl::RegistryPrefork?

2009-03-02 Thread Michael Peters
Perrin Harkins wrote: I'm not sure if that's accurate or not, but setting a $SIG{__DIE__} handler should work fine. You don't even need to use a __DIE__ handler. mod_perl will place any runtime errors into $r-notes('error-notes'). I don't like my errors going to the browser (only really

Re: get backtrace emailed when code dies running under ModPerl::RegistryPrefork?

2009-03-02 Thread Adam Prime
Michael Peters wrote: You don't even need to use a __DIE__ handler. mod_perl will place any runtime errors into $r-notes('error-notes'). I don't like my errors going to the browser (only really works if your content is HTML anyway) but for the email I usually use an Apache cleanup handler.

Re: get backtrace emailed when code dies running under ModPerl::RegistryPrefork?

2009-03-02 Thread Michael Peters
Adam Prime wrote: This was news to me, so i went to the docs. According to them, you have to explicitly enable this behavior. see: http://perl.apache.org/docs/2.0/api/Apache2/Log.html#C_Apache2__Const__LOG_TOCLIENT_ Is that still accurate? I don't know about mod_perl2, but I didn't

Re: tracking a coredump problem

2009-03-02 Thread Carl Brewer
eric.b...@barclayscapital.com wrote: Carl, I may have missed it, but did you say at what point you were seeing the segfault? I assume you mean at startup, but can you confirm? Not at startup, it happens after 'a while'. It's very hard to track, and I am stumped at trying to get a core file

[no subject]

2009-03-02 Thread 刘书强

svn commit: r749253 - in /perl/modperl/branches/threading: ./ README-SVN RELEASE lib/Apache2/SizeLimit.pm t/conf/post_config_startup.pl

2009-03-02 Thread torsten
Author: torsten Date: Mon Mar 2 09:36:53 2009 New Revision: 749253 URL: http://svn.apache.org/viewvc?rev=749253view=rev Log: Merged revisions 732889-732891,732893,732895,736207-736208,736213-736218 via svnmerge from https://svn.eu.apache.org/repos/asf/perl/modperl/trunk r732889 |