Wednesday, January 19, 2011

STATA: Debugging with trace

Having a problem figuring out where a pesky line of code is hiding? Type -set trace on- and run your do file again. You'll get more ridiculously verbose output than you can shake a stick at, which will take twice as long to run but let you know in excruciating detail exactly what Stata was thinking. Just remember to -set trace off- when you're done.

2 comments:

  1. Do you know how you can see exactly which .do file Stata is executing at the time an error occurs?

    ReplyDelete