I learned a long time ago that the key to debugging applications -- esp. CGI applications -- is to log information about the state of the program to a file. Using an in house logger with the ability to change verbosity (preferably from the program, i.e. so you can have somebody e-mail you the logs if there are problems) allows looking at a script and seeing exactly what is going on. It can be a pain setting it up, but there is nothing sweeter then saying "there's been 2 emails, and we see from the log that function send_email was called twice"
Want to support the EFF and FSF by buying cool stuff? Click here.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link or
or How to display code and escape characters
are good places to start.
|
