Support Requests item #446022, was opened at 2001-07-30 10:37
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=203152&aid=446022&group_id=3152
Category: Scripting: Tcl/ADP
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: M Gordon (zgorm)
Assigned to: Dossy Shiobara (dossy)
Summary: Viewing debug info within a broken adp
Initial Comment:
Hello All,
I am completely new to Aolserver, so please forgive me
if the answer to my question is obvious.
I am having a hell of a time trying to debug my adp
application. Whenever there is an error in an adp that
I have written, instead of seeing a useful error
message when I view that page, all I get is a blank
page.
I already tried to find the answer to my problem in
the online docs, which told me to do the following:
# TCL Config
ns_section "ns/server/${servername}/tcl"
ns_param ClientDebug 10.0.0.1
Supposedly by setting the value of the ClientDebug
param to the ip address of the client wishing to view
the error information (10.0.0.1), any person who views
a bad adp from that ip should see an error trace. So I
restarted Aolserver and prayed, but this did not work.
Does anyone know why that is?
Also, if you know of a better way to get debug
information, that would be really helpful too.
Thanks.
-Matt
----------------------------------------------------------------------
>Comment By: M Gordon (zgorm)
Date: 2001-07-30 12:49
Message:
Logged In: YES
user_id=284892
the server.log does catalog some database errors, but i am
not really interested in having to tail -f that file while
i am developing. especially since this will mean that i
will see errors from other people developing other pages on
the server.
what i really want is to be able to see error information
when i point my browser to a page with an error on it.
this must be possible. how do people develop sites in adp
if it isn't?
----------------------------------------------------------------------
Comment By: Dossy Shiobara (dossy)
Date: 2001-07-30 11:04
Message:
Logged In: YES
user_id=21885
Have you tried checking the log/server.log file for your
Tcl errors?
-- Dossy
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=203152&aid=446022&group_id=3152
