# A Modern C Development Environment | Interrupt

**URL:** <https://community.memfault.com/t/a-modern-c-development-environment-interrupt/702>\
**Category:** Blog\
**Created:** [August 9, 2023, 9:15pm UTC](https://community.memfault.com/t/a-modern-c-development-environment-interrupt/702 "2023-08-09T21:15:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![SSchmidt](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@SSchmidt](https://community.memfault.com/u/SSchmidt)\
**Post date:** [January 18, 2024, 7:39am UTC](https://community.memfault.com/t/a-modern-c-development-environment-interrupt/702/7 "2024-01-18T07:39:06Z")

</div>

This is a great article on how to setup a C development environment.

I prefer to have the debugger run natively on the host and connect to it by adding  
“gdbTarget”: “host.docker.internal:2331”,  
to the configuration in launch.json. This way I do not have to mount the USB-probe in the container.

---

_[View the full topic](https://community.memfault.com/t/a-modern-c-development-environment-interrupt/702)._