# How can I obtain the complete traces of an execution?

**URL:** <https://discuss.ocaml.org/t/how-can-i-obtain-the-complete-traces-of-an-execution/11616>\
**Category:** Learning\
**Created:** [March 8, 2023, 11:18am UTC](https://discuss.ocaml.org/t/how-can-i-obtain-the-complete-traces-of-an-execution/11616 "2023-03-08T11:18:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![geoffder](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/geoffder/32/3310_2.png) [@geoffder](https://discuss.ocaml.org/u/geoffder)\
**Post date:** [March 8, 2023, 5:04pm UTC](https://discuss.ocaml.org/t/how-can-i-obtain-the-complete-traces-of-an-execution/11616/2 "2023-03-08T17:04:13Z")

</div>

You can prefix your build command with `OCAMLRUNPARAM=b` as previously [answered](https://discuss.ocaml.org/t/how-to-get-useful-backtraces/1279/4). I alias `OCAMLRUNPARAM=b dune` to `dunetrace` for slightly more convenient use when I want to turn traces on for debugging.

---

_[View the full topic](https://discuss.ocaml.org/t/how-can-i-obtain-the-complete-traces-of-an-execution/11616)._