Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pkg mode Segmentation fault in 1.11.2 #56862

Open
andferrari opened this issue Dec 18, 2024 · 2 comments
Open

Pkg mode Segmentation fault in 1.11.2 #56862

andferrari opened this issue Dec 18, 2024 · 2 comments

Comments

@andferrari
Copy link

On my ubuntu 24.04 computer, julia 1.11.2 crashes when in Pkg mode.
Julia is installed with juliaup. Pkg package works correctly.
There is no problem with 1.11.1.

$ julia
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.11.2 (2024-12-01)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

julia> versioninfo()
Julia Version 1.11.2
Commit 5e9a32e7af2 (2024-12-01 20:02 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 56 × Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
  WORD_SIZE: 64
  LLVM: libLLVM-16.0.6 (ORCJIT, broadwell)
Threads: 1 default, 0 interactive, 1 GC (on 56 virtual cores)
Environment:
  LD_LIBRARY_PATH = /usr/local/cuda-12.2/lib64:/usr/lib/x86_64-linux-gnu:/usr/local/cuda/lib64
julia> 
julia> # here I press the ] 
(@v1.11) pkg> Segmentation fault (core dumped)
$
@giordano
Copy link
Contributor

giordano commented Dec 18, 2024

Can you please run this with a debugger like gdb and find where the segfault is happening? Without more information this is going to be hard to be actionable. Also, try to unset LD_LIBRARY_PATH before starting Julia, e.g. start Julia with

LD_LIBRARY_PATH="" julia

@andferrari
Copy link
Author

For now, I am unable to reproduce the bug and I don't understand what has changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants