Enhancing Julia Debugging: Entry Points
还没有人认领这个 Issue。
评估
调研方向
该 issue 未指定文件、测试或代码入口点。首先定位 debugger 在编译模式下的 breakpoint 处理逻辑，然后定义手动指定的入口点应如何触发自动 stepping，直到到达红色 breakpoint。完成的标准是：已明确规定所提议的入口点 workflow，并针对相关调试模式完成覆盖。
由索引模型根据 Issue 内容生成。
描述
Debugging in Julia can be significantly enhanced, particularly in dealing with large codebases, through the introduction of entry points.
When debugging extensive Julia code, the compiled mode proves to be practically useful due to its speed and freedom from conflicts with libraries. In contrast, the non-compiled mode easily becomes impractical due to its slow performance or potential library conflicts.
However, a notable drawback of the compiled mode is that it ignores breakpoints within sub-functions. Consequently, users are required to manually navigate through the code until the relevant subfunction is reached.
When repeatedly debugging functions at a deep level, the current approach involves placing breakpoints at all calling functions, necessitating multiple manual step-ins and step-outs to reach the desired section of code. This significantly disrupts the debugging flow and makes it challenging to maintain focus on the specific problem at hand.
Consider this idea: instead of manually stepping in and out at every level, why not let the Julia Debugger handle it automatically? If, instead of setting red breakpoints at all calling functions, users could designate orange entrance points, the debugger could identify these entry points and execute step-ins and step-outs automatically until the first red breakpoint is encountered.
Introducing this feature would greatly enhance the debugging experience, providing a more streamlined and focused approach to identifying and resolving issues in the code.
Note: If you can create a function that can find the entry points on its own, we’ll have a debugger that’s as good as those in other languages, but with the speed of Julia! This would make Julia even more appealing. However, I see this as a second step. First, I strongly suggest to improve the efficiency by manually setting the entry points. Right now, debugging in Julia becomes difficult as the project gets bigger.
- 主要语言
- Julia
- 星标
- 515
- 派生
- 50
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
JuliaDebug/Debugger.jl 的其他 Issue
-
tagbot-manual
难度 2/5 1-3 小时 新手友好度 72/100
JuliaDebug/Debugger.jl#410 ·
-
难度 4/5 3-5 天 新手友好度 48/100
JuliaDebug/Debugger.jl#423 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 45/100
JuliaDebug/Debugger.jl#422 ·
-
难度 3/5 1-2 天 新手友好度 55/100
JuliaDebug/Debugger.jl#418 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 55/100
JuliaDebug/Debugger.jl#417 · 1 条评论 ·
查看 JuliaDebug/Debugger.jl 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
JuliaDebug/Cthulhu.jl#716 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 66/100
-
难度 2/5 1-3 小时 新手友好度 68/100
rafaqz/DimensionalData.jl#1253 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
osrep/Runes2P.jl#283 ·
维护者通常 1 天内回复