# Debug segfault in libnvvm

**URL:** <https://forums.developer.nvidia.com/t/debug-segfault-in-libnvvm/184295>\
**Category:** CUDA Programming and Performance\
**Created:** [July 21, 2021, 10:12am UTC](https://forums.developer.nvidia.com/t/debug-segfault-in-libnvvm/184295 "2021-07-21T10:12:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Robert\_Crovella](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/robert_crovella/32/14043_2.png) [@Robert\_Crovella](https://forums.developer.nvidia.com/u/Robert_Crovella)\
**Post date:** [July 21, 2021, 7:26pm UTC](https://forums.developer.nvidia.com/t/debug-segfault-in-libnvvm/184295/2 "2021-07-21T19:26:15Z")

</div>

I’m going to assume that you have some other, perhaps shorter input file that your process can handle correctly. If not, you may be simply misusing/misapplying libnvvm.

This would be roughly analogous to the case where some aspect of the compile toolchain (e.g. `nvcc` or one of its sub-tools) was segfaulting during compilation. I can’t speak to your case specifically, but with respect to `nvcc` that is never expected behavior. So the usual advice there is to [file a bug](https://forums.developer.nvidia.com/t/how-to-report-a-bug/67911). If you choose to do that, you’ll likely be asked for a full test case (just setting expectations.)

I’m not able to offer further debug suggestions other than trial-and-error/divide-and-conquer/binary search. Others may have ideas.

---

_[View the full topic](https://forums.developer.nvidia.com/t/debug-segfault-in-libnvvm/184295)._