Stata The Stata listserver
[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

st: RE: trace


From   "Scott Merryman" <[email protected]>
To   <[email protected]>
Subject   st: RE: trace
Date   Thu, 23 Dec 2004 10:52:55 -0600

-set tracedepth #- will restrict the number of subroutines that are traced.
-set tracedepth 1- , for example, only the main program will be traced.  See
[P] trace, for more details and other options.

Scott


> -----Original Message-----
> From: [email protected] [mailto:owner-
> [email protected]] On Behalf Of Eric DeRosia
> Sent: Thursday, December 23, 2004 10:29 AM
> To: [email protected]
> Subject: st: trace
> 
> 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
> 


*
*   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/



© Copyright 1996–2024 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index