I’m currently trying to make the switch from Matlab to Julia 1.5.3. I am currently working with Atom/Juno (Atom 1.54.0, uber-juno 0.3.0) because of it’s similarity to the the Matlab editor. While I like many things in Julia, I’m having a really hard time debugging my code. Coming from Matlab, I am u…

Thanks. Very helpful. Just to clarify, adding the child modules of Base seems to add more code to the list that is run in compiled mode. So should I do the following? Or is the second line not needed given that the third line will be executed? using JuliaInterpreter, MehodAnalysis push!(JuliaInter…

I am assuming ... @enter myfunc() # or @enter MyPackage.myfunc() ... would replace the call ... myfunc() ... within my code. Is this correct?

I just run the @enter line in the REPL directly, without putting it in the code.

Or is the second line not needed given that the third line will be executed? Correct How does this compare with clicking on the + sign in the Run and Debug area of VSCode and adding MyPackage? I think that they are identical (meaning that VS Code executes that push! command internally). One o…

I tried a variety of strategies to make debugged code run faster. The bottom line is that adding my own packages to the list of compiled packages in VSCode works quite well, but the code you suggested does not seem to work in my system. Here is what I did: Commented or uncommented all commands re…

If you’re using VS Code rather than the command-line Debugger.jl, it’s possible that VS Code is using an internal vendored copy of JuliaInterpreter and so the manual commands I described won’t work. (In essence there may be two JuliaInterpreters and my commands add the packages to the wrong one.) Ad…

Thanks so much for your continued help here Tim. I am using VSCode so it is difficult to explicitly run things in the same REPL as the debugger. As a result I’m having a hard time figuring out how to add Base to the compiled modules in my situation. (Where would I run the push! code you sent?) Addit…

Although I just saw your last message in this thread. So I guess it is a losing battle. But would be great to figure out if there was a way to use the VSCode debugger in the Matlab-like way. I think it would really enhance the user experience for a lot of people.

@pfitzseb @davidanthoff any tips?

Take a look at the Julia: Compiled Code section in the VS Code debugger pane: [image] It allows you to set modules or functions as compiled/interpreted, which has the exact same effect as the function calls Tim outlined above.

Debugging extremely slow

Tooling

gmantegna June 27, 2023, 8:20pm 49

Amazing, thank you so much!!

Topic		Replies	Views
Extremely slow debugging in VS Code New to Julia question , debugging , vscode	53	3503	January 20, 2025
Debugger status and future plans? Community question , debug	122	10624	February 7, 2022
Improve debugger GUI to help adoption? Juno	31	4302	March 24, 2020
VSCode Julia debugger usability VS Code debug	19	3428	July 20, 2022
Julia debugging is extremely slow New to Julia debug	102	3516	March 24, 2026

Debugging extremely slow

Related topics