within a eval block without
completing it
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 ex
@perl.apache.org
Subject: RE: apache mod_perl aborted a process within a eval block without
completing it
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
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
hanks
Ron
From: [EMAIL PROTECTED] on behalf of Perrin Harkins
Sent: Fri 12/7/2007 4:41 PM
To: Ronald Dai.
Cc: modperl@perl.apache.org
Subject: Re: apache mod_perl aborted a process within a eval block without
completing it
On Dec 7, 2007 3:51 PM, Ronald Dai. &l
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
