# Debugging segfault when calling versioninfo()

**URL:** <https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239>\
**Category:** General Usage\
**Created:** [February 15, 2024, 7:51am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239 "2024-02-15T07:51:58Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulmelis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paulmelis/32/35063_2.png) [@paulmelis](https://discourse.julialang.org/u/paulmelis)\
**Post date:** [February 15, 2024, 7:51am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/1 "2024-02-15T07:51:59Z")

</div>

I’m having some issues that Julia (1.10.x, both from the official tarball or from juliaup, probably same binary) segfaults when I do a simple `versioninfo()`. This is on a compute node of an HPC system, so there might be weird library and/or filesystem things going on, or even something related to supported CPU instruction sets and/or features.

```julia
snellius paulm@gcn29 08:47 ~$ which julia
/sw/arch/RHEL8/EB_production/2023/software/juliaup/1.14.5-GCCcore-12.3.0/bin/julia
snellius paulm@gcn29 08:47 ~$ julia
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.10.1 (2024-02-13)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

julia> versioninfo()
Segmentation fault

```

On a different node type (AMD vs Intel CPU, etc) of the same HPC system things don’t crash:

```julia
julia> versioninfo()
Julia Version 1.10.1
Commit 7790d6f0641 (2024-02-13 20:41 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 96 × AMD EPYC 7F72 24-Core Processor
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-15.0.7 (ORCJIT, znver2)
Threads: 1 default, 0 interactive, 1 GC (on 96 virtual cores)
Environment:
  LD_LIBRARY_PATH = /sw/arch/RHEL8/EB_production/2023/software/GCCcore/12.3.0/lib64

```

I had seen this before and thought it was fixed by updating to the latest Julia version, but alas. What would be a good strategy to figure out what is going wrong here? Are there any relevant debug or trace flags I can set?

---

<div class="post-metadata">

**Author:** ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)\
**Post date:** [February 15, 2024, 7:55am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/2 "2024-02-15T07:55:00Z")

</div>

Are the libraries loaded through LD\_LIBRARY\_PATH compatible with what julia expects? What happens if you invoke julia like `LD_LIBRARY_PATH="" julia`?

---

<div class="post-metadata">

**Author:** ![paulmelis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paulmelis/32/35063_2.png) [@paulmelis](https://discourse.julialang.org/u/paulmelis)\
**Post date:** [February 15, 2024, 7:59am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/3 "2024-02-15T07:59:33Z")

</div>

Well, you’re onto something…

```julia
snellius paulm@gcn29 09:33 ~$ LD_LIBRARY_PATH= julia
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.10.1 (2024-02-13)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

julia> versioninfo()
Julia Version 1.10.1
Commit 7790d6f0641 (2024-02-13 20:41 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 72 \ufffd\ufffd Intel(R) Xeon(R) Platinum 8360Y CPU @ 2.40GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-15.0.7 (ORCJIT, icelake-server)
Threads: 1 default, 0 interactive, 1 GC (on 72 virtual cores)
Environment:
  LD_LIBRARY_PATH = 

```

Edit: initially tested on the wrong node type, updated now

---

<div class="post-metadata">

**Author:** ![paulmelis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paulmelis/32/35063_2.png) [@paulmelis](https://discourse.julialang.org/u/paulmelis)\
**Post date:** [February 15, 2024, 8:03am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/5 "2024-02-15T08:03:27Z")

</div>

Still interesting that there seems to be a node-dependent effect, though. I’ll do some more testing

---

<div class="post-metadata">

**Author:** ![paulmelis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paulmelis/32/35063_2.png) [@paulmelis](https://discourse.julialang.org/u/paulmelis)\
**Post date:** [February 15, 2024, 8:44am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/6 "2024-02-15T08:44:16Z")

</div>

Found the apparent culprit, it’s a libunwind module that gets pulled in as dependency for some software:

```julia
snellius paulm@gcn29 09:43 /gpfs/work4/1/viz/paulm/stevens-rb/Ra1e11$ m list

Currently Loaded Modules:
  1) 2023 2) GCCcore/12.3.0 3) juliaup/1.14.5-GCCcore-12.3.0 4) libunwind/1.6.2-GCCcore-12.3.0

 

snellius paulm@gcn29 09:43 /gpfs/work4/1/viz/paulm/stevens-rb/Ra1e11$ julia
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.10.1 (2024-02-13)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

julia> versioninfo()
Segmentation fault

snellius paulm@gcn29 09:43 /gpfs/work4/1/viz/paulm/stevens-rb/Ra1e11$ m unload libunwind/1.6.2-GCCcore-12.3.0
snellius paulm@gcn29 09:43 /gpfs/work4/1/viz/paulm/stevens-rb/Ra1e11$ julia
               _
   _ _ _(_)_ | Documentation: https://docs.julialang.org
  (_) | (_) (_) |
   _ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` | |
  | | |_| | | | (_| | | Version 1.10.1 (2024-02-13)
 _/ |\ __'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |

julia> versioninfo()
Julia Version 1.10.1
Commit 7790d6f0641 (2024-02-13 20:41 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 72 \ufffd\ufffd Intel(R) Xeon(R) Platinum 8360Y CPU @ 2.40GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-15.0.7 (ORCJIT, icelake-server)
Threads: 1 default, 0 interactive, 1 GC (on 72 virtual cores)
Environment:
  LD_LIBRARY_PATH = /sw/arch/RHEL8/EB_production/2023/software/GCCcore/12.3.0/lib64

```

---

<div class="post-metadata">

**Author:** ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)\
**Post date:** [February 15, 2024, 10:07am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/7 "2024-02-15T10:07:24Z")

</div>

I don’t know why the issue manifests with `versioninfo()` in particular, but it makes sense that a wrong libunwind causes this kind of issue - it’s very fundamental to how julia handles errors, so presumably anything that could make use of it would break.

---

<div class="post-metadata">

**Author:** ![paulmelis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/paulmelis/32/35063_2.png) [@paulmelis](https://discourse.julialang.org/u/paulmelis)\
**Post date:** [February 15, 2024, 10:14am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/8 "2024-02-15T10:14:44Z")

</div>

It’s not just in `versioninfo()`, btw:

```julia
snellius paulm@gcn29 11:14 /projects/1/viz/paulm/stevens-rb/Ra1e11$ julia --project=. -e 'using HDF5'
Segmentation fault

```

---

<div class="post-metadata">

**Author:** ![Sukera](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@Sukera](https://discourse.julialang.org/u/Sukera)\
**Post date:** [February 15, 2024, 10:35am UTC](https://discourse.julialang.org/t/debugging-segfault-when-calling-versioninfo/110239/9 "2024-02-15T10:35:18Z")

</div>

Yes, that’s not too surprising. libunwind is very fundamental, so if the version is wrong, pretty much anything can go wrong anywhere.

My suggestion would be to use a clean `LD_LIBRARY_PATH`.