On Dec 7, 2007 5:01 PM, Ronald Dai. <[EMAIL PROTECTED]> wrote:
> Because it is somehting like
>
> eval{ do something; warn " warning message"} or die "dying message";
>
> Neither warning message nor dying message was logged.
That could mean that it crashed before the warning, or it could mean
som
Perrin:
I looks you are rightI might have tested something else;-)
Thanks
Ron
From: [EMAIL PROTECTED] on behalf of Perrin Harkins
Sent: Fri 12/7/2007 4:53 PM
To: Ronald Dai.
Cc: modperl@perl.apache.org
Subject: Re: apache mod_perl aborted a process wit
Because it is somehting like
eval{ do something; warn " warning message"} or die "dying message";
Neither warning message nor dying message was logged.
Thanks
Ron
From: [EMAIL PROTECTED] on behalf of Perrin Harkins
Sent: Fri 12/7/2007 4:57 PM
To: Ronald Da
Perrin:
I think there must be something made the apache or mod_perl very unhappy so
that it killed the process in the middle.
Thanks
Ron
From: Ronald Dai. [mailto:[EMAIL PROTECTED]
Sent: Fri 12/7/2007 4:45 PM
To: Perrin Harkins
Cc: modperl@perl.apache
I think you've responded to the wrong thread here...
On Dec 7, 2007 4:49 PM, Ronald Dai. <[EMAIL PROTECTED]> wrote:
> For a
> eval{} or die "" block if the message of die was not logged, I guess the
> process got aborted within the eval block
That's a pretty big guess. How do you know it did
On Dec 7, 2007 4:45 PM, Ronald Dai. <[EMAIL PROTECTED]> wrote:
> eval could not catch exit() calls but exit() calls within eval actually
> won't have the process exit...I just tested it.
You must have tested something else, because exit() does cause a
process to leave an eval block. Maybe you tri
Perrin:
Good infoI will make note of itBut our situation might be a bit
different. Within the block that failed is a MIME::Lite::SMTP mail sending
call. The content of the mail is standardized for everyone except for name etc.
For most people, it either does not fail or fail with error
eval could not catch exit() calls but exit() calls within eval actually won't
have the process exit...I just tested it. I am not aware of any $SIG{__DIE__}
handlersince in most cases the eval competed normally, I kind suspect that
it is mod_perl or apache that is doing something...
Thanks
On Dec 6, 2007 8:36 PM, Silent <[EMAIL PROTECTED]> wrote:
> # my mod_rerite.conf
> # section 1
> RewriteEngine On
> RewriteCond %{HTTP_USER_AGENT} Firefox [OR]
> RewriteCond %{HTTP_USER_AGENT} lwp-request [OR]
> RewriteRule ^/mp3/aaa\.mp3$/mp3/aaa.html
>
> # section 2
> RewriteCond %{H
On Dec 7, 2007 3:51 PM, Ronald Dai. <[EMAIL PROTECTED]> wrote:
> Could someone help me to explain under what circumstances, the mod_perl or
> apache would abort a process within an eval block without letting the code
> complete the block?
A segfault or an exit().
Your perl is pretty old, so it's
mod_perl version: 1.27
perl version: 5.6.1
apache version: 1.3.26
Question:
We got some 500 server error because an ' eval{...} or die "[EMAIL
PROTECTED]" ' block failed.
Normally when the eval block failed, the process will die with $@ message
logged because of the die statement after th
Really interesting mail - if you're on perl monks, please cross post it
to there - there are a few UTF gurus who could help you out there.
If you're not, drop me a line and I'll post it for you.
Clint
On Fri, 2007-12-07 at 10:10 -0800, Fred Moyer wrote:
> Greetings mod_perl list,
>
> I've been
Greetings mod_perl list,
I've been having fun with dtrace, and I most recently used it to see
what files are being accessed by mod_perl during requests. I've
preloaded all the modules in my application that I know about into
startup.pl, but when I startup my httpd server and make a request, I
13 matches
Mail list logo
