# Painful debugging in VSC
**URL:** https://discourse.julialang.org/t/painful-debugging-in-vsc/49597
**Category:** General Usage
**Created:** [November 4, 2020, 7:55pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597 "2020-11-04T19:55:23Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [November 4, 2020, 7:55pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/1 "2020-11-04T19:55:23Z")
Is it only me or others share this experience that debugging in VSC is becoming more and more painful? See the example of the attached fig. The code flow did not stop at the breakpoint. It did land directly at the position of the yellow triangle. This is happening awfully frequently with not even stopping inside a function. Furthermore, when there is an error it kills me the REPL. It even randomly gives errors (and kills the REPL) when stepping (F10).
Julia 1.5 on Windows
---
### Author:  [@juliohm](https://discourse.julialang.org/u/juliohm)
#### Post date: [November 4, 2020, 8:30pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/2 "2020-11-04T20:30:23Z")
I have also experienced this situation in which the breakpoint is simply ignored by the debugger. I don’t know what is happening, it would be nice to learn.
---
### Author:  [@juliohm](https://discourse.julialang.org/u/juliohm)
#### Post date: [July 4, 2023, 1:04pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/3 "2023-07-04T13:04:58Z")
For instance, I noticed is that the syntax `@enter x |> f` ignores breakpoints, whereas the syntax `@enter f(x)` respects breakpoints.
cc: @davidanthoff
---
### Author:  [@TI36XPro](https://discourse.julialang.org/u/TI36XPro)
#### Post date: [July 4, 2023, 1:16pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/4 "2023-07-04T13:16:16Z")
The couple times I’ve tried to use the Julia extension debugger in VSC I’ve had similar issues (hanging, passing over break points, etc.). However, this is not a problem for me because I find I can effectively debug my packages using a combination of `@show`, Infiltrator, and the [ref](https://www.youtube.com/watch?v=g-iOOhh2U6o&t=10s) trick. So I basically never use the debugger.
---
### Author:  [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 4, 2023, 1:33pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/5 "2023-07-04T13:33:52Z")
Opened [this issue](https://github.com/julia-vscode/docs/issues/72) a month ago. Being able to debug with VSC is a **fundamental** feature but unfortunately it seems that debugging is the ugly duckling (hope that the translation of “Patinho Feio” is right) of the Julia tooling.
---
### Author:  [@juliohm](https://discourse.julialang.org/u/juliohm)
#### Post date: [July 4, 2023, 1:41pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/6 "2023-07-04T13:41:30Z")
I have a different experience myself nowadays. The debugger in VSCode is working like a charm, except for the case I shared above with `@enter x |> f` syntax.
---
### Author:  [@joa-quim](https://discourse.julialang.org/u/joa-quim)
#### Post date: [July 4, 2023, 2:07pm UTC](https://discourse.julialang.org/t/painful-debugging-in-vsc/49597/7 "2023-07-04T14:07:35Z")
Not mine ☹ I very often have to kill the VSC repl to make the breakpoints being respected again. And wait 100 secs for the package gets compiled.