JuliaDebug / JuliaDebug/Debugger.jl

Debugger unusable anymore due to warnings

Open
#337 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
514
Forks
50
Avg merge
9d 9h
Merged PRs (30d)
1

Description

In the last week the debugger (run from the REPL inside VSCode) has stopped being usable. One issue is I constantly get warnings like the following:

1|debug> 
┌ Warning: Tuple{Plots.var"##plot#188", Base.Pairs{Symbol, V, Tuple{Vararg{Symbol, N}}, NamedTuple{names, T}} where {V, N, names, T<:Tuple{Vararg{Any, N}}}, typeof(plot), Vararg{Any}} was not found
└ @ Revise ~/.julia/packages/Revise/t6Vjc/src/packagedef.jl:1111
┌ Warning: Tuple{Plots.var"##plot#188", Base.Pairs{Symbol, V, Tuple{Vararg{Symbol, N}}, NamedTuple{names, T}} where {V, N, names, T<:Tuple{Vararg{Any, N}}}, typeof(plot), Vararg{Any}} was not found
└ @ Revise ~/.julia/packages/Revise/t6Vjc/src/packagedef.jl:1111
┌ Warning: Tuple{Plots.var"##plot#188", Base.Pairs{Symbol, V, Tuple{Vararg{Symbol, N}}, NamedTuple{names, T}} where {V, N, names, T<:Tuple{Vararg{Any, N}}}, typeof(plot), Vararg{Any}} was not found
└ @ Revise ~/.julia/packages/Revise/t6Vjc/src/packagedef.jl:1111

There are a number of other issues: breakpoints being triggered in the wrong function, macros not working, etc.

I don't remember seeing these issues 3–6 months ago so I'm not sure what's changed.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the debugger from the Julia REPL inside VSCode and capture the Revise warning reported at packagedef.jl:1111. Investigate the reported warning, incorrect breakpoint locations, and non-working macros together, then verify that warnings stop and breakpoints and macros behave correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.