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 !
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:[EMAIL PROTECTED] > > Try putting: > > use Error; > > 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. > > Lee Goddard wrote: > > > > Please could Log/Log4perl/Config.pm line 619 offer a stack backtrace > > as well as barfing? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel
