Kristoffer Carlsson
Kristoffer Carlsson
From https://github.com/JuliaDebug/Debugger.jl/pull/263 ```diff - |About to run: (inner_kw)(1, 2; c=5) + |About to run: (var"#inner_kw##kw"())((c = 5,), inner_kw, 1, 2) ``` ```diff -In inner_kw(a, b; c, d) at ui.jl:56 +|In...
Would be nice with a keyboard shortcut like `N` to show the native code of the current function.
```jl julia> @enter sin(2.0) In sin(x) at special/trig.jl:30 >30 absx = abs(x) 31 if absx < T(pi)/4 #|x| ~ w add __FRAME__.pc 1] __FRAME__.pc: 4 1|debug> w add __FRAME__.framedata.ssavalues[5] 1]...
See https://discourse.julialang.org/t/debugger-jl-bp-does-not-work/22154/2
```jl julia> @enter f(2) In f(x) at REPL[8]:1 1 f(x) = sin(x) About to run: (sin)(2) ``` The `(sin)` might as well be printed as `sin`.
After https://github.com/JuliaDebug/JuliaInterpreter.jl/pull/524 it is possible to set breakpoint on type constructors but this fail when a type constructor is called with specific parameters: ```jl julia> struct Constructor{T} x::T end julia>...
Sometimes macros expand to a lot of garbage that one is rarely interested in (see the logging macros). If possible, having a mode of the debug commands that steps through...
I don't really see a case where you would rather have this off when debugging.
Sometimes when you want to diagnose a stack overflow error it would be convenient to be able to set a maximum stack depth (like 30), run the function, get a...