# Make the work of GC visible?

**URL:** <https://discourse.julialang.org/t/make-the-work-of-gc-visible/24642>\
**Category:** General Usage\
**Created:** [May 27, 2019, 8:13am UTC](https://discourse.julialang.org/t/make-the-work-of-gc-visible/24642 "2019-05-27T08:13:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)\
**Post date:** [May 27, 2019, 8:13am UTC](https://discourse.julialang.org/t/make-the-work-of-gc-visible/24642/1 "2019-05-27T08:13:36Z")

</div>

Is there are recommended way to make the work of GC visible? Like a command line option or compile time option? (or putting breakpoints in /bin/julia and run in gdb …).

I’m (still) hunting a sig11 bug in (my) code and to me it looks like GC.preserve doesn’t what it should do.

---

<div class="post-metadata">

**Author:** ![jpsamaroo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jpsamaroo/32/46804_2.png) [@jpsamaroo](https://discourse.julialang.org/u/jpsamaroo)\
**Post date:** [May 28, 2019, 7:49pm UTC](https://discourse.julialang.org/t/make-the-work-of-gc-visible/24642/2 "2019-05-28T19:49:11Z")

</div>

I would start with building julia-debug from source (`make -j${nproc} julia-debug`), and then run julia-debug under gdb/lldb/rr. Valgrind may also be of use, but I’ve never used it myself.