CM's point, that errors may occur long after starting the program,
illustrates a difficulty with current debugging methods: you have to have
some idea where the program failed to efficiently turn on trace. Most often
you do, but sometimes you do not. High on my wish list for Stata is the
ability to have a program that produce an error optionally display the line
or line # where the program fails or to turn on trace at the previous line.
Fred Wolfe
At 01:48 PM 12/2/2003 -0600, you wrote:
Hi all,
I regularly program .do files that take hours or days to run. Sometimes
they return error messages and I have to debug them. I wonder if there is
a way to (1) output a date and time at the time an error message appears
(which invariably stops my .do file from continuing), and (2) close a log
file that was started (preferably including the error message and
date/time; this allows me to access the log file remotely to check its
status)...
As always, I have used "findit" to no avail.
CM
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
Fred Wolfe
National Data Bank for Rheumatic Diseases
Wichita, Kansas
Tel (316) 263-2125 Fax (316) 263-0761
[email protected]
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
