try setting -tracedepth- (set to 1 if you really believe it is your code)
Rich Goldstein
Eric DeRosia wrote:
I'm new to Stata programming, and I'm having a problem that makes me miss
programming in SAS (a feeling I never thought I would have). When I'm
debugging a program in Stata, error messages are generated without telling
me what command generated them. So, I set trace on. And then I get *tons*
of output. Even the most innocuous command (e.g., means) generates a
boat-load of log. I see the utility in that behavior for some situations --
I really do. But I believe it is safe to initially assume that the source
of the error is my code, not an ado file. Hence my question: is there a way
to set trace on without tracing through ado files?
- Eric
Eric DeRosia,
Assistant Professor,
Marriott School of Management
Brigham Young University
*
* 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/
