use strict
use warnings

Will help you to save most of debug time.

And. perhaps you still have option C.

Thaz, if you need some quick test, you can
make the form data becomes uri escaped. or
boundary based. So you can test it inline.
with warn, and die. you will really what
error is happened at which line.

But that's a side effect. You can't use
CGI.pm to handle this sort of data, unless
you know how to make the escaped string
becomes STDIN.

Rgds,
Connie





----- Original Message -----
From: "Saurabh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, August 04, 2002 3:17 PM
Subject: Help Needed: Debugging web applications in perl+cgi+php+mysql on apache+ssl


Hello,

I am not sure if this is the right mailing list to ask this question or not but I have 
exhausted all my resource
(various search engines, including google, some newsgroups and various websites) and I 
could not find a convincing
answer/solution to my question/problem.

Pls direct me to the appropriate mailing list if this is not the correct mailing list 
for this question.
So, here is the scenario:

Basically, I have to create a secure web site functional from most browsers that is 
written in perl+cgi+php+mysql(for
various fcunctionalities  like accessing database etc). How do I debug a web 
application that uses Perl, CGI, PHP, HTML,
Apache+ SSL?

There are mainly two ways that I could found and atleast one of them is not very 
efficient and the second one I am not
sure about.
(a)First solution is to use:
use CGI::Carp qw(fatalsToBrowser); I am not very comfortable with this solution.
(b)The second solution is to use a perl debugger called ptkdb. I am not sure how much 
useful is this ptkdb in debugging
a web appplication.

I have not used any of these solutions. It is a big application and would probably 
need lot of debugging.

Here are my questions to gurus:
(1) Am I correct that anyone of these approaches can be used to debug web application
(2) Which of these is a better approach to debug web application keeping in mind that 
it is a huge application and would
need lot of debugging.
(3) Can anyone suggest me anything else which is better than the two approaches listed 
above.
(4) Can anyone tell me what are the pros and cons of using the two approaches.

I greatly appreciate all the help.

thx,
Saurabh












-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to