# Should vscode debugger work in REPL for included functions?

**URL:** <https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379>\
**Category:** Tooling\
**Tags:** debug, vscode\
**Created:** [December 5, 2025, 1:49pm UTC](https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379 "2025-12-05T13:49:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![carpetguy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carpetguy/32/219665_2.png) [@carpetguy](https://discourse.julialang.org/u/carpetguy)\
**Post date:** [December 5, 2025, 1:49pm UTC](https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379/1 "2025-12-05T13:49:29Z")

</div>

I’m running the vscode REPL and including scripts (via includet or include) which have functions defined. However, if I set breakpoints in the script files (say in `myFunc`) and do `@run myFunc()`, the breakpoint is skipped. In fact, if there is an error in the function, it doesn’t seem to be happy to step into the function (i.e. doesn’t highlight the line of code with the error). Is this expected?

Alternatively, using `@enter myFunc()` does step in and lets me debug as I would expect.

Note I don’t see my code in the compiled section of the debug pane (what would it be under as it’s a script not a module?).

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [December 5, 2025, 7:53pm UTC](https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379/2 "2025-12-05T19:53:13Z")

</div>

Try disabling all compiled functions/modules. It’s likely that that list has bitrotted and isn’t applicable to recent Julia versions anymore.

---

<div class="post-metadata">

**Author:** ![carpetguy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carpetguy/32/219665_2.png) [@carpetguy](https://discourse.julialang.org/u/carpetguy)\
**Post date:** [December 8, 2025, 4:58pm UTC](https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379/3 "2025-12-08T16:58:58Z")

</div>

Thanks this was indeed the problem. Should have thought to try it out before asking.

---

<div class="post-metadata">

**Author:** ![carpetguy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carpetguy/32/219665_2.png) [@carpetguy](https://discourse.julialang.org/u/carpetguy)\
**Post date:** [December 8, 2025, 10:07pm UTC](https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379/4 "2025-12-08T22:07:12Z")

</div>

Is that list of compiled code just for when we’re debugging? As it seems that @run ends up being slow, but just calling my functions is quite quick.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [December 8, 2025, 10:24pm UTC](https://discourse.julialang.org/t/should-vscode-debugger-work-in-repl-for-included-functions/134379/5 "2025-12-08T22:24:34Z")

</div>

> [@carpetguy](#):
>
> Is that list of compiled code just for when we’re debugging?

Yes.