TraceCalls.jl icon indicating copy to clipboard operation
TraceCalls.jl copied to clipboard

A debugging and profiling tool for Julia

Results 18 TraceCalls.jl issues
Sort by recently updated
recently updated
newest added

The last two months of Revise.jl updates have changed its internals, which this package depended on. @timholy Can I please ask for some pointers? I unfortunately have much less time...

I think this package is awesome, in fact I just recently looked everywhere for a package like this. One thing that could be awesome would be plotting capabilities for traces...

Great package! This is just an FYI for others. This package doesn't work in IJulia, but will if https://github.com/JuliaLang/IJulia.jl/pull/641 gets merged. The call that triggers the error is in ClobberingReload...

This should enable tracing functions like `Base.length`

@jrevels I'm growing increasingly dissatisfied with my current tracing procedure (mostly that it's slow to parse all of these source files), and Cassette.jl looks super-promising :+1:. Is there any limitation...

We could write a macro for checking that a condition holds post-hoc: ```julia @check_arguments some_function some_condition_involving_the_arguments begin ... some code end ``` This suggests a macro `@with_args trace expression_using_args`

@timholy Revise.jl achieves speed by mutating data structures, but TraceCalls.jl achieves it by memoizing function results. I already found out the hard way that this is a dangerous mix. Can...

For instance `@show_highlighted Int x->x

`@trace_log a b a*b` can store `a*b` as a special object, while passing `a` and `b` as keyword-arguments.

We could generate a list of "safe" functions to trace.