comment on

A few ideas:

Look in your Web server logs. That's where these errors will show up.
CGI::Carp will make errors show up in your browser, but generally not compile-time errors.
If you can't get to your Web server logs, try wrapping your CGI script in a small wrapper that will send errors to the browser. For example, if your CGI program is called dosomething, name this shell script dosomething-debug, make it executable, then run this script from your browser to see errors.
```
#!/bin/sh -e

exec 2>&1
printf "Content-type: text/plain\n\n"
echo "Current directory:"
pwd
exec /path/to/dosomething
[download]
```
--
sgifford's Web page

In reply to Re: Debugging CGI/PERL by sgifford
in thread Debugging CGI/PERL by Trihedralguy

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:

& &

< <

> >

[ [

] ]
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`