# Seg fault with OpenMP backend

**URL:** <https://pyfr.discourse.group/t/seg-fault-with-openmp-backend/976>\
**Category:** Errors\
**Tags:** openmp\
**Created:** [7 November 2023 03:59 UTC](https://pyfr.discourse.group/t/seg-fault-with-openmp-backend/976 "2023-11-07T03:59:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![royaero](https://yyz2.discourse-cdn.com/free1/user_avatar/pyfr.discourse.group/royaero/32/589_2.png) [@royaero](https://pyfr.discourse.group/u/royaero)\
**Post date:** [7 November 2023 21:29 UTC](https://pyfr.discourse.group/t/seg-fault-with-openmp-backend/976/2 "2023-11-07T21:29:38Z")

</div>

Update:

- tried re-installing the libomp-dev and libgomp1 packages from Ubuntu through sudo apt-get
- tried the actions on this thread by using SHARED=1 NOBLAS=1 instead of STATIC=0 BLAS=0 [Failed to run example cases using openmp as backend](https://pyfr.discourse.group/t/failed-to-run-example-cases-using-openmp-as-backend/649/25)
- tried all of libxsmmext.so, libxsmm.so.1, and libxsmm.so.1.17.0 as the PYFR\_XSMM\_LIBRARY\_PATH variable similar to this thread [OpenMP xsmm, kernel mul has no providers](https://pyfr.discourse.group/t/openmp-xsmm-kernel-mul-has-no-providers/511) but same seg fault for the latter 3 and a different error for the former

Wondering if I am missing something? (Is it an issue with AMD processors? As the following thread happens upon the same problem it seems [When using AMD CPU with PyFR](https://pyfr.discourse.group/t/when-using-amd-cpu-with-pyfr/943))

Thank you if anybody may have any tips!

---

_[View the full topic](https://pyfr.discourse.group/t/seg-fault-with-openmp-backend/976)._