Bug #16544 for CGI-Application-Plugin-DebugScreen: conflicts with ::Plugin::Session

Fri Dec 16 10:04:58 2005 Guest - Ticket created

Subject:

conflicts with ::Plugin::Session

I like this idea. Thanks for your work on it! It didn't work for me because produced output even when there was no problem. This seemed to be because I'm also using the Session plugin, which calls a flush() function at "DESTROY" time, which in turn using a database handle. Somehow this module interferes there. I tried modifying your source to not register the __DIE__ handler, and instead call the debugging function from withing an "error_mode()" routine. That solved the CGI::Session problem, but the stack trace was then wrong-- it tracked back to where we finally died in error_mode().... It's a tricker problem to provide a good stack trace than I realized! Mark

Mon Dec 19 22:52:18 2005 Guest - Correspondence added

From:

markstos [...] cpan.org

[guest - Fri Dec 16 10:04:58 2005]: Show quoted text

> I like this idea. Thanks for your work on it! > > It didn't work for me because produced output even when there was no > problem. This seemed to be because I'm also using the Session > plugin, which calls a flush() function at "DESTROY" time, which in > turn using a database handle. Somehow this module interferes there. > > I tried modifying your source to not register the __DIE__ handler, and > instead call the debugging function from withing an "error_mode()" > routine. > > That solved the CGI::Session problem, but the stack trace was then > wrong-- it tracked back to where we finally died in > error_mode()....

I can confirm this was fixed in 0.02. Thanks! Mark

Tue Dec 20 00:07:05 2005 Guest - Correspondence added

[guest - Mon Dec 19 22:52:18 2005]: Show quoted text

> [guest - Fri Dec 16 10:04:58 2005]: >

> > I like this idea. Thanks for your work on it! > > > > It didn't work for me because produced output even when there was no > > problem. This seemed to be because I'm also using the Session > > plugin, which calls a flush() function at "DESTROY" time, which in > > turn using a database handle. Somehow this module interferes there. > > > > I tried modifying your source to not register the __DIE__ handler, and > > instead call the debugging function from withing an "error_mode()" > > routine. > > > > That solved the CGI::Session problem, but the stack trace was then > > wrong-- it tracked back to where we finally died in > > error_mode()....

> > I can confirm this was fixed in 0.02. Thanks! > > Mark

I love CGI::App. Thank you for a wonderful framework. atsushi

Wed Jan 19 07:39:26 2011 nekokak [...] cpan.org - Correspondence added

closed

Wed Jan 19 07:39:27 2011 The RT System itself - Status changed from 'new' to 'open'

Wed Jan 19 07:39:27 2011 nekokak [...] cpan.org - Status changed from 'open' to 'resolved'