Re: Debugging Apache::ASP
Hi there, On Wed, 6 Dec 2000, Differentiated Software Solutions Pvt. Ltd., wrote: We are having problems debugging an ASP program. [snip] How do others tackle this ?? % do_something(); % % print STDERR $omething; % % do_something_else(); % % print STDERR $omething_else; % How do people track "use of uninitialised variable". I initialise all my variables. 73, Ged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debugging Apache::ASP
On Wed, 6 Dec 2000, Differentiated Software Solutions Pvt. Ltd., wrote:
Hi,
We've been using Apache::ASP over the past one month.
We are having problems debugging an ASP program.
We have set the debug level to 3 but still.
At debug level 3, the line in which the error occurs is displayed.
But if we have multiple statements withing % and % tags then, the error display
only gives only one line number (line number of the first statement) is displayed. We
are finding it very difficult to identify the exact line where the error has occured.
In general we find Apache::ASP support for debugging quite poor. Are there any tools
which we are missing out ??
How do others tackle this ??
How do people track "use of uninitialised variable".
use Carp ();
$SIG{__WARN__} = \Carp::cluck;
Thanks,
S Muthu Ganesh
Differentiated Software Solutions Pvt. Ltd.,
176, Ground Floor, 6th Main,
2nd Block, RT Nagar,
Bangalore - 560032
Visit us at www.diffsoft.com
_
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://jazzvalley.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debugging Apache::ASP
"Differentiated Software Solutions Pvt. Ltd.," wrote: Hi, We've been using Apache::ASP over the past one month. We are having problems debugging an ASP program. We have set the debug level to 3 but still. At debug level 3, the line in which the error occurs is displayed. But if we have multiple statements withing % and % tags then, the error display only gives only one line number (line number of the first statement) is displayed. We are finding it very difficult to identify the exact line where the error has occured. In general we find Apache::ASP support for debugging quite poor. Are there any tools which we are missing out ?? How do others tackle this ?? How do people track "use of uninitialised variable". Don't do "use strict", do PerlSetVar UseStrict 1. Use Apache::ASP v2.03 or greater as it had significant debugging enhancements. If you are having problem with your debug output, let me see it, and I may be able to help interpret. The line numbers are usually right on. --Josh _ Joshua Chamas Chamas Enterprises Inc. NodeWorks free web link monitoring Huntington Beach, CA USA http://www.nodeworks.com1-714-625-4051 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
