# \[FPM\] Interactive debugging

**URL:** <https://fortran-lang.discourse.group/t/fpm-interactive-debugging/10506>\
**Category:** Visual Studio Code\
**Created:** [November 20, 2025, 8:35am UTC](https://fortran-lang.discourse.group/t/fpm-interactive-debugging/10506 "2025-11-20T08:35:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![davidpfister](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/davidpfister/32/3949_2.png) [@davidpfister](https://fortran-lang.discourse.group/u/davidpfister)\
**Post date:** [November 20, 2025, 10:53am UTC](https://fortran-lang.discourse.group/t/fpm-interactive-debugging/10506/4 "2025-11-20T10:53:30Z")

</div>

You can have a look at what @matthiasnoback wrote on this [topic](https://github.com/matthiasnoback/fortran-workshop/blob/main/docs/VS-Code-Fortran-Debugging.md). In the end, it’s similar to what @moriglia proposed with the `–runner` option. This approach can be automated by adding a task into VSCode as discussed in that [thread](https://fortran-lang.discourse.group/t/easier-debugging-with-vscode-and-fpm/8850). That discussion on GitHub may also be of help [Integrating fpm with text editors (Sublime, Atom, VS Code) · fortran-lang/fpm · Discussion #479 · GitHub](https://github.com/fortran-lang/fpm/discussions/479) .

If you go for the install trick: `build` and `install` can be executed together using a .rsp file and creating your custom command.

---

_[View the full topic](https://fortran-lang.discourse.group/t/fpm-interactive-debugging/10506)._