Yes, I'm not getting useful backtraces... that has several reasons: (1) I'm using OS X and LLVM 3.5 (my fault). But I'm also running on Linux, and backtraces are working fine there. (2) I'm running in parallel, and failing @test or @assers often leads to a hang instead of an error (or backtrace). (3) I'm also running distributed via MPI, and may even have errors in my program leading to deadlocks.
Currently I'm adding many "info" statements. I'm sure there must be a better way... Maybe in 0.4. -erik On Sat, Sep 13, 2014 at 6:14 PM, Tim Holy <[email protected]> wrote: > 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 > -- Erik Schnetter <[email protected]> http://www.perimeterinstitute.ca/personal/eschnetter/
