Hi,
I’m curious about why the debugger behaves as it does in the following case. I’m debugging the file https://github.com/FluxML/model-zoo/blob/master/vision/vae_mnist/vae_mnist.jl and I’m putting a breakpoint at row 94 (args = Args(; kws…)). The call stack looks as expected “Main → train”. However, when I step forward (i.e. execture “Args(; kws…)”), the call stack becomes “Main → train → #train#10”, where does this new level come from? Furthermore, it seems like I am stuck in this extra frame:
I have a second breakpoint at row 107 (loader = get_data(args.batch_size)) but I cannot reach that breakpoint. As soon as I hit row 100 (@info “Training on GPU”) the debugger enters file logging.jl#350 (*) and I am never (**) able to return to the breakpoint of row 107.
(*) This is probably the same issue as: https://github.com/julia-vscode/julia-vscode/issues/1667
(**) Note that I’m not sure if “never” is because of super slow debugger or because of some weird reason such as breakpoint being set in frame “train” but since I’m stuck in frame “#train#10” it never actually hits it (I don’t really know how debuggers work).
I’m using Julia 1.6.1