From: Lee G. <LGo...@UK...> - 2007-06-28 12:50:25
|
Thanks for the tip, John: I don't recall the module, but it looks like a good quick-fix, quicker than tracking-down and editing every version of L4p I install ! =20 But I'd still like the shortmess near configuration file errors, because they're pretty common end-user errors. > -----Original Message----- > From: John ORourke [mailto:joh...@o-...] >=20 > Try putting: >=20 > use Error; >=20 > in one of your modules/scripts - it will override the warn/die handlers > globally, so unless Log4perl overrides them again it will give you a > stack trace. >=20 > Lee Goddard wrote: > > > > Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace > > as well as barfing? |