Re: Re: CAP::DebugScreen and ErrorDocument

On Sat, 24 Dec 2005, Mark Stosberg <mark@xxxxxxxxxxxxxxx> wrote:
> On 2005-12-24, Cees Hek <ceeshek@xxxxxxxxx> wrote:
> > I ignored the test failure and installed anyway.  However, the author
> > should be notified I guess...
>
> Done:
>
> http://rt.cpan.org/NoAuth/Bug.html?id=16727

Still having problems with this module. The fix allowed installation, 
and providing the line 'use CAP::DebugScreen' is placed in myapp.pm 
rather than the instance script then the application runs until a fatal 
is encountered (but see below), but the following 2 lines appear each 
time in the Apache error log:

[error] [client 127.0.0.1] [Sat Dec 24 16:56:58 2005] myapp.cgi: \t(in 
cleanup) Can't call method "commit" on unblessed reference at 
C:/usr/local/site/lib/CGI/Session/Driver/DBI.pm line 122 during global 
destruction., referer: 
http://127.0.0.1/cgi-bin/MyApp/myapp.cgi?rm=display_record;id=4

[error] [client 127.0.0.1] DESTROY created new reference to dead object 
'CGI::Session::Driver::mysql' during global destruction., referer: 
http://127.0.0.1/cgi-bin/MyApp/myapp.cgi?rm=display_record;id=4

These do not appear if 'use CAP::DebugScreen' is commented out. And I 
still get the 500 Internal Server Error page rather than 
CAP::DebugScreen functionality if I deliberately introduce a run-time 
fatality (eg calling non-existent template in a runmode).

CGI::Carp::DebugScreen works fine in the same application if used in 
place of CAP::DebugScreen. Hope it's not just me.
--
Richard Jones
Leeds, UK
mailto:ra.jones@xxxxxxxxxxxxxxx

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx