# IDE: step-through debugging for macro-generated function?

**URL:** https://discourse.julialang.org/t/ide-step-through-debugging-for-macro-generated-function/63899
**Category:** Tooling
**Tags:** debug, macros, metaprogramming, vscode
**Created:** [July 1, 2021, 2:59pm UTC](https://discourse.julialang.org/t/ide-step-through-debugging-for-macro-generated-function/63899 "2021-07-01T14:59:52Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![greatpet](https://avatars.discourse-cdn.com/v4/letter/g/e495f1/32.png) [@greatpet](https://discourse.julialang.org/u/greatpet)
#### Post date: [July 1, 2021, 2:59pm UTC](https://discourse.julialang.org/t/ide-step-through-debugging-for-macro-generated-function/63899/1 "2021-07-01T14:59:52Z")

</div>

I recently tried using VSCode debugger to “step into” a function from an external package, but VSCode pointed me to a strange code location. Eventually I figured out that the function was not written out, but was generated by a macro in the package involving `eval` calls.

Would it be possible for future versions of the VSCode extension to show the generated function body and allow the user to step through the lines when debugging?