I take it you're not getting a useful backtrace from your error? That fact alone would be worth reporting, if you have a simple test case.
If you run into troubles by not getting enough samples, you can always decrease the delay down to 10 microseconds or so. The default setting of 1 ms is designed to avoid any substantive performance impact, but for tracing you might prefer more samples. --Tim On Saturday, September 13, 2014 02:38:53 PM Elliot Saba wrote: > Unfortunately, `@profile` is the closest we have now. You could > conceivably call `@profile` from within a `try` so that you can print out > the profile results at the end. > -E > > On Sat, Sep 13, 2014 at 12:13 PM, Erik Schnetter <[email protected]> > > wrote: > > I want to trace the execution of a Julia program to find out where an > > error occurs. Is there something like a @trace macro, similar to @time or > > @profile? > > > > -erik
