# Debugging extremely slow

**URL:** <https://discourse.julialang.org/t/debugging-extremely-slow/53801>\
**Category:** Tooling\
**Tags:** question\
**Created:** [January 22, 2021, 7:18pm UTC](https://discourse.julialang.org/t/debugging-extremely-slow/53801 "2021-01-22T19:18:00Z")\
**Posts on this page:** 1\
**Showing post:** 56

<div class="post-metadata">

**Author:** ![mariusd](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mariusd/32/23231_2.png) [@mariusd](https://discourse.julialang.org/u/mariusd)\
**Post date:** [September 4, 2023, 7:51pm UTC](https://discourse.julialang.org/t/debugging-extremely-slow/53801/56 "2023-09-04T19:51:53Z")

</div>

Debugging in Julia is just decent for the code I have tested. The problem is rather we don’t document all the features we provide, and some of them are essential. This must be improved, because we end-up spending more time guiding users in forums than creating a complete documentation.

Imagine a new user who wants to debug. He starts here: [Debugging · Julia in VS Code (julia-vscode.org)](https://www.julia-vscode.org/docs/dev/userguide/debugging/). They need to imediatelly know all available configs for debbuging and all external tools like Debugger.jl and Infiltrator.jl.  
Here is a modest PR in this regard: [Minimally document externall debugging tools by MariusDrulea · Pull Request #77 · julia-vscode/docs (github.com)](https://github.com/julia-vscode/docs/pull/77).

Improving the docs menu will help as well: [Include headings level 3 in the menu, on click · Issue #75 · julia-vscode/docs (github.com)](https://github.com/julia-vscode/docs/issues/75)

---

_[View the full topic](https://discourse.julialang.org/t/debugging-extremely-slow/53801)._