# Juno Debugger ignores breakpoints

**URL:** <https://discourse.julialang.org/t/juno-debugger-ignores-breakpoints/25988>\
**Category:** Juno\
**Created:** [July 3, 2019, 3:15pm UTC](https://discourse.julialang.org/t/juno-debugger-ignores-breakpoints/25988 "2019-07-03T15:15:08Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)\
**Post date:** [July 4, 2019, 2:52pm UTC](https://discourse.julialang.org/t/juno-debugger-ignores-breakpoints/25988/7 "2019-07-04T14:52:48Z")

</div>

Have you tried to check the “Run in compile mode” box of Juno’s debugger?

> [@\[ANN\] Juno 0.8.7](https://discourse.julialang.org/t/ann-juno-0-8-7/24682):
>
> Hey folks, Juno 0.8.7 is out and brings an updated Debugger along with a few bugfixes and small features: Features Setting breakpoints in files does not require Revise anymore. Run in Compiled Mode toggle when debugging ([#299](https://github.com/JunoLab/Juno.jl/issues/299)). Both Break on Exception and Break on Uncaught Exception are now implemented. Search in Workspace/Documentation panes is automatically focused ([#200](https://github.com/JunoLab/atom-ink/pull/200)). Added return-from-goto command ([#170](https://github.com/JunoLab/atom-ink/issues/170)). stdlib paths printed in the REPL are now clickable. Packages in the Open Packa…

My understanding is that if the slower part of your code is in a function different of that which you are `@enter`ing - and you don’t step deliberately into that function - the performance of the debugging mode will not be spoiled that much if you do that (although it will always be slower than the “normal” mode anyway).

---

_[View the full topic](https://discourse.julialang.org/t/juno-debugger-ignores-breakpoints/25988)._