Catching Errors

[-Brad-]

Insted of display Server error Id like to display something meaningful that
will assist me in debuging the problem without having to look at the server
error log.
If i use Carp qw(fatalsToBrowser)
It helps a little, but is there a way I can display similar to what would be
seen in the error_log,
eg
Missing right curly bracket at line 20.

Thanks

 

[Gunnar Hjalmarsson]

Insted of display Server error Id like to display something
meaningful that will assist me in debuging the problem without
having to look at the server error log.
If i use Carp qw(fatalsToBrowser)

Suppose you mean

use CGI::Carp qw(fatalsToBrowser);

It helps a little, but is there a way I can display similar to what
would be seen in the error_log,
eg Missing right curly bracket at line 20.

That is a fatal error, which should be captured by fatalsToBrowser().
Personally I have experienced significant differences in how different
versions of CGI::Carp behaves.

If it's more convenient to you, you may want to keep a 'private' error
log by using the carpout() function. See the CGI::Carp documentation
about how it works.

 

[-Brad-]

Ahh ok thanks for the reply!
Maybe I should make sure I have the latest version of the CGI module
installed.

Cheers

Insted of display Server error Id like to display something
meaningful that will assist me in debuging the problem without
having to look at the server error log.
If i use Carp qw(fatalsToBrowser)

Suppose you mean

use CGI::Carp qw(fatalsToBrowser);

It helps a little, but is there a way I can display similar to what
would be seen in the error_log,
eg Missing right curly bracket at line 20.

That is a fatal error, which should be captured by fatalsToBrowser().
Personally I have experienced significant differences in how different
versions of CGI::Carp behaves.

If it's more convenient to you, you may want to keep a 'private' error
log by using the carpout() function. See the CGI::Carp documentation
about how it works.