# Enhancing Ocaml Debugging Experience in Visual Studio Code

**URL:** <https://discuss.ocaml.org/t/enhancing-ocaml-debugging-experience-in-visual-studio-code/12236>\
**Category:** Learning\
**Tags:** ocamldebug, compiler, opam, build, dune\
**Created:** [May 26, 2023, 1:19pm UTC](https://discuss.ocaml.org/t/enhancing-ocaml-debugging-experience-in-visual-studio-code/12236 "2023-05-26T13:19:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![nojb](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/nojb/32/519_2.png) [@nojb](https://discuss.ocaml.org/u/nojb)\
**Post date:** [May 26, 2023, 2:42pm UTC](https://discuss.ocaml.org/t/enhancing-ocaml-debugging-experience-in-visual-studio-code/12236/2 "2023-05-26T14:42:29Z")

</div>

The only support for debugging inside VS Code is [GitHub - hackwaly/ocamlearlybird: OCaml debug adapter](https://github.com/hackwaly/ocamlearlybird/) but sadly it is not being actively maintained (judging by the README it only supports 4.11 and 4.12). And in any case since it is an adaptor for `ocamldebug` it only supports bytecode.

Until better alternatives come along, I suggest you get used to the time-tested debugging technique practiced by OCaml experts and beginners alike with unsurpassed effectiveness: [`printf` debugging.](https://www.azquotes.com/quote/721056)

Cheers,  
Nicolas

---

_[View the full topic](https://discuss.ocaml.org/t/enhancing-ocaml-debugging-experience-in-visual-studio-code/12236)._