# 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:** 54

<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, 3:33pm UTC](https://discourse.julialang.org/t/debugging-extremely-slow/53801/54 "2023-09-04T15:33:46Z")

</div>

> [@tim.holy](#):
>
> What do you do if you want to step into a function defined in another package? Once you get into compiled mode, stepping in and breakpoints are no longer supported.

Usually I don’t. If someone wants to do debug `SomePackage` for whatever reason, he simply has to

```julia
using SomePackage
union!(JuliaInterpreter.compiled_modules, setdiff(Base.loaded_modules_array(), [Main, SomePackage]))

```

Note your code has to be adjusted a bit: `union!(JuliaInterpreter.compiled_modules, setdiff(Base.loaded_modules_array(), [Main]))`

Question:  
Beside `Base.loaded_modules_array()`, do we also need to step in each loaded module with `child_modules(...)`?

---

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