# Limit \`catch\_backtrace()\` to function handling the exception

**URL:** <https://discourse.julialang.org/t/limit-catch-backtrace-to-function-handling-the-exception/106649>\
**Category:** General Usage\
**Created:** [November 23, 2023, 10:39pm UTC](https://discourse.julialang.org/t/limit-catch-backtrace-to-function-handling-the-exception/106649 "2023-11-23T22:39:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![SteffenPL](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/steffenpl/32/206270_2.png) [@SteffenPL](https://discourse.julialang.org/u/SteffenPL)\
**Post date:** [November 24, 2023, 12:50am UTC](https://discourse.julialang.org/t/limit-catch-backtrace-to-function-handling-the-exception/106649/2 "2023-11-24T00:50:12Z")

</div>

You could also check out AbbreviatedStackTraces.jl which aims give a good overview of the relevant lines.

Of course, it is quite a difficult problem in general to select the most relevant bits. While it is clear in your example, the situation becomes less clear if not all relevant code is in one file.

---

_[View the full topic](https://discourse.julialang.org/t/limit-catch-backtrace-to-function-handling-the-exception/106649)._