<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://www.webmaster-forums.net/crss/node/1011721" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title></title>
    <link>https://www.webmaster-forums.net/crss/node/1011721</link>
    <description></description>
    <language>en</language>
          <item>
    <title></title>
    <link>https://www.webmaster-forums.net/serverside-scripting/script-debugger#comment-1067312</link>
    <description> &lt;p&gt;Thanks for your hepl richard, the fatals to browser should be very useful &lt;img src=&quot;https://www.webmaster-forums.net/misc/smileys/smile.png&quot; title=&quot;Smiling&quot; alt=&quot;Smiling&quot; class=&quot;smiley-content&quot; /&gt;&lt;/p&gt;
 </description>
     <pubDate>Thu, 13 Jul 2000 06:42:08 +0000</pubDate>
 <dc:creator>minton</dc:creator>
 <guid isPermaLink="false">comment 1067312 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title>Forgot something.</title>
    <link>https://www.webmaster-forums.net/serverside-scripting/script-debugger#comment-1067303</link>
    <description> &lt;p&gt;Add a die command to the end of your open calls, that way you know if it is failing.&lt;/p&gt;
&lt;p&gt;Example:&lt;/p&gt;
&lt;p&gt;&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;$file = &amp;quot;/this/is/a/file.txt&amp;quot;;&lt;br /&gt;&lt;br /&gt;open(FILE,&amp;quot;&amp;lt;$file&amp;quot;) || die &amp;quot;Cannot open file $file.&amp;nbsp; Reasons: $!&amp;quot;;&lt;br /&gt;close(FILE);&lt;/code&gt;&lt;/div&gt;&#039;&lt;/p&gt;
&lt;p&gt;The above code will print what is in quotations if the open call does not work.  It will also exit the script.&lt;/p&gt;
&lt;p&gt;Richard&lt;/p&gt;
 </description>
     <pubDate>Thu, 13 Jul 2000 01:55:28 +0000</pubDate>
 <dc:creator>richjb</dc:creator>
 <guid isPermaLink="false">comment 1067303 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title>Solutions...</title>
    <link>https://www.webmaster-forums.net/serverside-scripting/script-debugger#comment-1067302</link>
    <description> &lt;p&gt;There are quite a few things you can do to check your code.&lt;/p&gt;
&lt;ol class=&quot;bb-list&quot;&gt;
&lt;li&gt; Add -w to the end of the path to perl.  This will print any suntax error that may be found to the log files (I think).  Beware: Although your script may work fine, this sometimes prints &quot;useless&quot; info to the log files each time the script is ran.  Suggestion: Only use on final script to see if there is anything you could change to make it better.
&lt;p&gt;Example:&lt;/p&gt;
&lt;p&gt;&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;#!/usr/bin/perl -w&lt;/code&gt;&lt;/div&gt;&#039;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt; Use the below code at the top of all your scripts (right under the path to PERL).  If a 500 error happens, you will not see the standard page.  Instead, you will see a page with an explination of what was wrong.  Usually this helps, but if your script is really messed up (or other reasons) it will just say &quot;Failed because of complications with scripts&quot; or something like that:
&lt;p&gt;&lt;div class=&quot;codeblock&quot;&gt;&lt;code&gt;BEGIN {&lt;br /&gt; use CGI::Carp qw(fatalsToBrowser);&lt;br /&gt;}&lt;/code&gt;&lt;/div&gt;&#039;&lt;/p&gt;
&lt;p&gt;Hope that helped.&lt;/p&gt;
&lt;p&gt;Richard&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
 </description>
     <pubDate>Thu, 13 Jul 2000 01:52:11 +0000</pubDate>
 <dc:creator>richjb</dc:creator>
 <guid isPermaLink="false">comment 1067302 at https://www.webmaster-forums.net</guid>
  </item>
  </channel>
</rss>
