I want to call cgi perl scripts on my web hosters server from
my HTML web pages (on the the web hosters server too).
It occurs sometimes (especially during development phase) that these cgi-perl scripts
didn't work like intended. They crash because e.g.

- syntax errors
- wrong or changing pathes
- unexpected user input
- ...

In former times I could easily track these crashes resp. try these cgi-scripts directly
with a telnet account/window.

However nowadays telnet access is mostly seen as a security hole a telnet account is not available any more.

How can I get the information about what went worng with a certain cgi-script otherwise ?

The system log shows (AFAIK) only a line similar to "cgi script myscript123.pl dumped at 11:34:23 time"

How can I get the information at which line the cgi script crashed and what the variable values were
at crash time ?

Imagine I entered in the HTML page a wrong path to the perl cgi script.
In which log file is it written?

Patricia

Patricia Mindanao wrote:

I want to call cgi perl scripts on my web hosters server from
my HTML web pages (on the the web hosters server too).
It occurs sometimes (especially during development phase) that these
cgi-perl scripts didn't work like intended. They crash because e.g.
>
- syntax errors
- wrong or changing pathes
- unexpected user input
- ...
>
In former times I could easily track these crashes resp. try these
cgi-scripts directly with a telnet account/window.
>
However nowadays telnet access is mostly seen as a security hole a
telnet account is not available any more.
>
How can I get the information about what went worng with a certain
cgi-script otherwise ?
>
The system log shows (AFAIK) only a line similar to "cgi script
myscript123.pl dumped at 11:34:23 time"
>
How can I get the information at which line the cgi script crashed and
what the variable values were at crash time ?
>
Imagine I entered in the HTML page a wrong path to the perl cgi
script. In which log file is it written?

use CGI::Carp qw(fatalsToBrowser warningsToBrowser);

This send any errors and warnings to the browser rather than just an
Error 500 (or similar) statement.

Search CPAN for more info.

Patricia Mindanao wrote:

I want to call cgi perl scripts on my web hosters server from
my HTML web pages (on the the web hosters server too).
It occurs sometimes (especially during development phase) that these cgi-perl scripts
didn't work like intended. They crash because e.g.
>
- syntax errors
- wrong or changing pathes
- unexpected user input
- ...
>
In former times I could easily track these crashes resp. try these cgi-scripts directly
with a telnet account/window.
>
However nowadays telnet access is mostly seen as a security hole a telnet account is not available any more.

Typically telnet access is then replaced with ssh access.

>
How can I get the information about what went worng with a certain cgi-script otherwise ?
>
The system log shows (AFAIK) only a line similar to "cgi script myscript123.pl dumped at 11:34:23 time"
>
How can I get the information at which line the cgi script crashed and what the variable values were
at crash time ?
>
Imagine I entered in the HTML page a wrong path to the perl cgi script.
In which log file is it written?

These are written to your web server logs. Location and name depends on
which web server you are using. Check the documentation of you web server.

>
Patricia
>

--

Len

Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com

On 09/27/2006 08:14 AM, Patricia Mindanao wrote:

I want to call cgi perl scripts on my web hosters server from
my HTML web pages (on the the web hosters server too).
It occurs sometimes (especially during development phase) that these cgi-perl scripts
didn't work like intended. They crash because e.g.
>
- syntax errors
- wrong or changing pathes
- unexpected user input
- ...
>
In former times I could easily track these crashes resp. try these cgi-scripts directly
with a telnet account/window.
>
However nowadays telnet access is mostly seen as a security hole a telnet account is not available any more.
>
How can I get the information about what went worng with a certain cgi-script otherwise ?
>
The system log shows (AFAIK) only a line similar to "cgi script myscript123.pl dumped at 11:34:23 time"
>
How can I get the information at which line the cgi script crashed and what the variable values were
at crash time ?
>
Imagine I entered in the HTML page a wrong path to the perl cgi script.
In which log file is it written?
>
Patricia
>

Find out what provisions your hosting service or company has for
providing you with your script errors. Hosting services do this differently.

For Perl scripts, in many cases you can start your program like this:

use CGI::Carp qw(fatalsToBrowser);

And that will cause fatal errors to be sent to the browser, but even
that is not guaranteed to work. Contact your hosting service.

P.S.
In many places, telnet has been replaced with "ssh." Ask them if you
have ssh access to your web-site account. But even then, ssh access does
not guarantee permission to view the error logs.

--
paduille.4058.mumia.w@earthlink.net

Patricia Mindanao wrote:

I want to call cgi perl scripts on my web hosters server from
my HTML web pages (on the the web hosters server too).
It occurs sometimes (especially during development phase) that these cgi-perl scripts
didn't work like intended. They crash because e.g.
>
- syntax errors
- wrong or changing pathes
- unexpected user input
- ...
>
In former times I could easily track these crashes resp. try these cgi-scripts directly
with a telnet account/window.
>
However nowadays telnet access is mostly seen as a security hole a telnet account is not available any more.
>
How can I get the information about what went worng with a certain cgi-script otherwise ?
>
The system log shows (AFAIK) only a line similar to "cgi script myscript123.pl dumped at 11:34:23 time"
>
How can I get the information at which line the cgi script crashed and what the variable values were
at crash time ?
>
Imagine I entered in the HTML page a wrong path to the perl cgi script.
In which log file is it written?
>
Patricia
>

My ISP allows secure Telnet access. I use Tera Term Pro as called from
a Tera Term secure shell addon. Both are quite old, but the security is
deemed sufficient by my ISP. Indeed, my ISP suggested these two and
told me where to find them.

Tera Term Pro is at
<http://hp.vector.co.jp/authors/VA002416/teraterm.html>. The Web site
for the secure shell addon is now defunct, but there are other addons
listed at this URL.

Discuss this with your hosting service before downloading and installing
any secure Telnet client. The service might prefer a particular client
software, or the service might just say that no Telnet access is
permitted under any circumstances. In the end, your service must grant
you Telnet access to its Web server.

--

David E. Ross
<http://www.rossde.com/>

Concerned about someone (e.g., Pres. Bush) snooping
into your E-mail? Use PGP.
See my <http://www.rossde.com/PGP/>