Thread: [Lxr-dev] [ lxr-Bugs-716701 ] $SIG{__WARN__} and mod_perl
Brought to you by:
ajlittoz
From: SourceForge.net <no...@so...> - 2003-04-07 12:01:25
|
Bugs item #716701, was opened at 2003-04-07 12:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 Category: Browsing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pavel Hlavnicka (pavel_hlavnicka) Assigned to: Nobody/Anonymous (nobody) Summary: $SIG{__WARN__} and mod_perl Initial Comment: To be honest, this problem brought many dreamless nights to me :) We run LXR in the mod_perl context together with another applications. Problem is simple. 1) LXR sets the $SIG{__WARN__} handler (i Common.pm), and it is, of course, global for the whole mod_perl context 2) the handler prints to the standard output(!!!) bu default (the $wwwdeug variable) As a result of this, in some environments (where LXR is running), under certain conditions (pretty rare in my case), some 'random' output is displayed in the page. (typically if something goes wrong in eval {}; block, what may be exactly what autor supposed). Uff, is think, $www debug should be cleared in the distribution, and setting the warning handler at all is a bit disputable, as some other application may be in trouble due this. Thanks for LXR Pavel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 |
From: SourceForge.net <no...@so...> - 2003-04-07 12:02:09
|
Bugs item #716701, was opened at 2003-04-07 12:17 Message generated for change (Comment added) made by pavel_hlavnicka You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 Category: Browsing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pavel Hlavnicka (pavel_hlavnicka) Assigned to: Nobody/Anonymous (nobody) Summary: $SIG{__WARN__} and mod_perl Initial Comment: To be honest, this problem brought many dreamless nights to me :) We run LXR in the mod_perl context together with another applications. Problem is simple. 1) LXR sets the $SIG{__WARN__} handler (i Common.pm), and it is, of course, global for the whole mod_perl context 2) the handler prints to the standard output(!!!) bu default (the $wwwdeug variable) As a result of this, in some environments (where LXR is running), under certain conditions (pretty rare in my case), some 'random' output is displayed in the page. (typically if something goes wrong in eval {}; block, what may be exactly what autor supposed). Uff, is think, $www debug should be cleared in the distribution, and setting the warning handler at all is a bit disputable, as some other application may be in trouble due this. Thanks for LXR Pavel ---------------------------------------------------------------------- >Comment By: Pavel Hlavnicka (pavel_hlavnicka) Date: 2003-04-07 12:17 Message: Logged In: YES user_id=302801 I need to tell, we are using 0.9.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 |
From: SourceForge.net <no...@so...> - 2004-07-12 17:25:21
|
Bugs item #716701, was opened at 2003-04-07 13:17 Message generated for change (Comment added) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 Category: Browsing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Pavel Hlavnicka (pavel_hlavnicka) Assigned to: Nobody/Anonymous (nobody) Summary: $SIG{__WARN__} and mod_perl Initial Comment: To be honest, this problem brought many dreamless nights to me :) We run LXR in the mod_perl context together with another applications. Problem is simple. 1) LXR sets the $SIG{__WARN__} handler (i Common.pm), and it is, of course, global for the whole mod_perl context 2) the handler prints to the standard output(!!!) bu default (the $wwwdeug variable) As a result of this, in some environments (where LXR is running), under certain conditions (pretty rare in my case), some 'random' output is displayed in the page. (typically if something goes wrong in eval {}; block, what may be exactly what autor supposed). Uff, is think, $www debug should be cleared in the distribution, and setting the warning handler at all is a bit disputable, as some other application may be in trouble due this. Thanks for LXR Pavel ---------------------------------------------------------------------- >Comment By: Malcolm Box (mbox) Date: 2004-07-12 18:25 Message: Logged In: YES user_id=215386 I've switched off wwwdebug in the CVS version, but the underlying problem of the use of global signal handlers is still there. Any suggestions for how to remove these would be welcome! ---------------------------------------------------------------------- Comment By: Pavel Hlavnicka (pavel_hlavnicka) Date: 2003-04-07 13:17 Message: Logged In: YES user_id=302801 I need to tell, we are using 0.9.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 |
From: SourceForge.net <no...@so...> - 2009-03-26 17:27:00
|
Bugs item #716701, was opened at 2003-04-07 13:17 Message generated for change (Settings changed) made by mbox You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Browsing Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Pavel Hlavnicka (pavel_hlavnicka) Assigned to: Nobody/Anonymous (nobody) Summary: $SIG{__WARN__} and mod_perl Initial Comment: To be honest, this problem brought many dreamless nights to me :) We run LXR in the mod_perl context together with another applications. Problem is simple. 1) LXR sets the $SIG{__WARN__} handler (i Common.pm), and it is, of course, global for the whole mod_perl context 2) the handler prints to the standard output(!!!) bu default (the $wwwdeug variable) As a result of this, in some environments (where LXR is running), under certain conditions (pretty rare in my case), some 'random' output is displayed in the page. (typically if something goes wrong in eval {}; block, what may be exactly what autor supposed). Uff, is think, $www debug should be cleared in the distribution, and setting the warning handler at all is a bit disputable, as some other application may be in trouble due this. Thanks for LXR Pavel ---------------------------------------------------------------------- >Comment By: Malcolm Box (mbox) Date: 2009-03-26 17:26 Message: $wwwdebug is now 0 in distribution. I agree the $SIG{__WARN__} abuse is dubious - but will leave this to individual sites to remove if wanted. ---------------------------------------------------------------------- Comment By: Malcolm Box (mbox) Date: 2004-07-12 18:25 Message: Logged In: YES user_id=215386 I've switched off wwwdebug in the CVS version, but the underlying problem of the use of global signal handlers is still there. Any suggestions for how to remove these would be welcome! ---------------------------------------------------------------------- Comment By: Pavel Hlavnicka (pavel_hlavnicka) Date: 2003-04-07 13:17 Message: Logged In: YES user_id=302801 I need to tell, we are using 0.9.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=390117&aid=716701&group_id=27350 |