Recently I’m promoting using Julia for our group’s next project. For context, we are choosing between Python and Julia for numerical simulations and prototype modeling. I advertised Julia’s speed, and did casual demos for some language features as well as the Juno IDE. One interesting observation i…

Hi @jlperla , I tried Infiltrator and liked it a lot. It’s equivalent to Matlab’s “keyboard” which I am familiar with. The scenario we do need a full visual debugger is, again, not to debug one’s own code, but to understand others’ code when there is no good documentation or clear architecture. When…

[image] Zhong_Pan: The scenario we do need a full visual debugger is, again, not to debug one’s own code, but to understand others’ code when there is no good documentation or clear architecture. I am 100% with you on the end-goal of a matlab debugger. It is outstanding and I live in it with…

I’m not going to promise any timeline, but we still plan to integrate the debugger into the VS Code extension at some point. We would automatically get a very good UI that way that we don’t have to maintain.

@davidanthoff Looking forward to it! I guess any improvement to JuliaInterpreter speed, as well as automatic switching between compiled mode vs. interpreted mode, etc. would still be useful in the VS Code extension, right?

Yes, whenever we get to work on this, we would just be using whatever debugger infrastructure exists at that point. What we need to do to enable this scenario in VS Code is write a debug adapter . We’ve started a little bit already, but this is not a small project, and right now we are focusing on p…

[image] jlperla: And it effectively would need to recompile the function each time you add a breakpoint. For reference this is. It normally a problem. That is generally cheap enough. It’s only voiding (part of) compile cache. Extreme worse case scenario is it takes as long as first run ti…

[image] jlperla: Inflitrator: everything is fast except you you can’t “step into” functions. @pfitzseb things a approach similar to MixedModeDebugger’s could be added to Infiltrator to allow this. (I’m not sure I see how to do that, exactly. But it feels right.)

[image] oxinabox: That is generally cheap enough. It’s only voiding (part of) compile cache My gut tells me you are right. Even if it is a little slow in some functions, it is due to an explicit user action. When people are exploring code, they can choose to set less breakpoints if they find…

I haven’t looked into those, but now that I know they exist I will.

I believe that Infiltrator is less experimental and pretty robust (while mixedmode is more likely to gain cool features, but has a cassette dependency and more fragile at the moment). So worth building the UI settings to make debuggers swappable (since they have different tradeoffs) but Infiltrator …

Improve debugger GUI to help adoption?

Tooling Juno

Topic		Replies	Views
Debugger status and future plans? Community question , debug	122	10353	February 7, 2022
Extremely slow debugging in VS Code New to Julia question , debugging , vscode	53	3316	January 20, 2025
Debugging extremely slow Tooling question	56	9871	September 5, 2023
VSCode Julia debugger usability VS Code debug	19	3378	July 20, 2022
How do you use debuggers? Community	138	27548	September 28, 2018

Improve debugger GUI to help adoption?

Related topics