ConfigLoader
Static::Simple
- Dumper
StackTrace
DefaultEnd
/;
=item *
-L<Catalyst::Plugin::Dumper>
-
-Allows you to easily use L<Data::Dumper> to dump variables
-to the logs, for example:
-
- $c->log->dumper($myvar);
-
-When running your application under the development server, the logs
-will be printed to your screen along with the other debug information
-generated by the C<-Debug> flag.
-
-=item *
-
L<Catalyst::Plugin::StackTrace|Catalyst::Plugin::StackTrace>
Adds a stack trace to the standard Catalyst "debug screen" (this is the
screen Catalyst sends to your browser when an error occurs).
-Note: L<Dumper|Catalyst::Plugin::Dumper> output appears on the console
-window where you issue the C<script/myapp_server.pl> command.
-L<StackTrace|Catalyst::Plugin::StackTrace> output appears in your
-browser.
+Note: L<StackTrace|Catalyst::Plugin::StackTrace> output appears in your
+browser, not in the console window from which you're running your
+application, which is where logging output usually goes.
=item *
.------------------------------------------------------------------------------.
| Catalyst::Plugin::ConfigLoader 0.07 |
| Catalyst::Plugin::Static::Simple 0.14 |
- | Catalyst::Plugin::Dumper 0.000002 |
| Catalyst::Plugin::StackTrace 0.04 |
| Catalyst::Plugin::DefaultEnd 0.06 |
'------------------------------------------------------------------------------'
Catalyst::Manual::Tutorial::Debugging - Catalyst Tutorial - Part 6: Debugging
-
-
=head1 OVERVIEW
This is B<Part 6 of 9> for the Catalyst tutorial.
=item 9
-L<Appendicies|Catalyst::Manual::Tutorial::Appendicies>
+L<Appendices|Catalyst::Manual::Tutorial::Appendices>
=back
-
=head1 DESCRIPTION
This part of the tutorial takes a brief look at the primary options
available for troubleshooting Catalyst applications.
-Note that when it comes to debugging and troubleshooting, there are two camps:
+Note that when it comes to debugging and troubleshooting, there are two
+camps:
=over 4
Catalyst is able to easily accommodate both styles of debugging.
-
-
=head1 LOG STATEMENTS
Folks in the former group can use Catalyst's C<$c-E<gt>log> facility.
-For example, if you add the following code to a controller action
-method:
+(See L<Catalyst::Log> for more detail.) For example, if you add the
+following code to a controller action method:
- $c->log->debug("This is a test log message");
+ $c->log->info("Starting the foreach loop here");
+
+ $c->log->debug("Value of $id is: ".$id);
Then the Catalyst development server will display your message along
-with the other debug output. To accomplish the same thing in a TTSite
+with the other debug output. To accomplish the same thing in a TTSite
view use:
[% Catalyst.log.debug("This is a test log message") %]
-You can also use L<Data::Dumper|Data::Dumper> in both Catalyst code
-(C<$c-E<gt>log-E<gt>dumper($myvar)>) and TT templates (C<[%
-Dumper.dump(book) %]> as discussed in earlier parts of the tutorial.
-
-
+You can also use L<Data::Dumper> in both Catalyst code (C<use
+Data::Dumper; $c-E<gt>log-E<gt>debug("$var is: ".Dumper($var));)>) and
+TT templates (C<[% Dumper.dump(book) %]>.
=head1 RUNNING CATALYST UNDER THE PERL DEBUGGER
-Members of the interactive debuggers fan club will also be at home with
+Members of the interactive-debugger fan club will also be at home with
Catalyst applications. One approach to this style of Perl debugging is
to embed breakpoints in your code. For example, open
C<lib/MyApp/Controller/Books.pm> in your editor and add the
and C<perldebtut>. You can also type C<h> or C<h h> at the debugger
prompt to view the built-in help screens.
-
-
=head1 AUTHOR
Kennedy Clark, C<hkclark@gmail.com>
Please report any errors, issues or suggestions to the author.
-Copyright 2006, Kennedy Clark, under Creative Commons License (L<http://creativecommons.org/licenses/by-nc-sa/2.5/>).
+Copyright 2006, Kennedy Clark, under Creative Commons License
+(L<http://creativecommons.org/licenses/by-nc-sa/2.5/>).
Version: .94
projects / catagits/Catalyst-Runtime.git / commitdiff