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.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__} handler....since in most cases the eval competed normally, I kind suspect that it is mod_perl or apache that is doing something... Thanks 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. <[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 possible you're seeing some long-ago-fixed bug here. But eval can't catch segfaults or exit() calls in any perl code. You could also have a $SIG{__DIE__} handler somewhere that is intercepting the error and not returning. - Perrin
