# Seg fault when using julia (pakcage installation, profiling)

**URL:** <https://discourse.julialang.org/t/seg-fault-when-using-julia-pakcage-installation-profiling/133991>\
**Category:** General Usage\
**Tags:** question, bug, error, segfault\
**Created:** [November 19, 2025, 2:02pm UTC](https://discourse.julialang.org/t/seg-fault-when-using-julia-pakcage-installation-profiling/133991 "2025-11-19T14:02:13Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Ahmed\_ALKAF](https://avatars.discourse-cdn.com/v4/letter/a/3e96dc/32.png) [@Ahmed\_ALKAF](https://discourse.julialang.org/u/Ahmed_ALKAF)\
**Post date:** [November 21, 2025, 1:45pm UTC](https://discourse.julialang.org/t/seg-fault-when-using-julia-pakcage-installation-profiling/133991/16 "2025-11-21T13:45:31Z")

</div>

In my case, I need the `LD_LIBRARY_PATH` for an application called Libero SoC.

The variable `LD_LIBRARY_PATH` used to be in bashrc but I removed it so I can run julia.  
Now every time I need to run Libero, I just do an export of `LD_LIBRARY_PATH` with the value that I need, this works and it doesn’t affect julia.

---

_[View the full topic](https://discourse.julialang.org/t/seg-fault-when-using-julia-pakcage-installation-profiling/133991)._