Perhaps something is failing before the debug window gets called, are you checking your error_log? For CGI::Application::Plugin::DebugScreen info check out Rapid Website Development with CGI::Application. On page four it has a short section titled "DevPopUp: A Unique Developer Tool". This section has a link to an example on Rhesa's CPAN pages.

Have you tried any debugging at all from the command line to see why the script is dying? Remember to check your error_log to see what is going on. Read up on use CGI::Carp qw(fatalsToBrowser);, but remember not to have this in production code.

Martin

In reply to Re: CGI::Application:: Plugin::DebugScreen by marto
in thread CGI::Application:: Plugin::DebugScreen by thind

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.