-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Provide an error message if LD_PRELOAD is set during a Julia build or startup #55487
Comments
Can you please provide more information about the system? CPU, operating system, etc... What are
Just to understand, how do you reproduce the same error when you're using prebuilt binaries? |
Is there an LD_LIBRARY_PATH or LD_PRELOAD by any chance that is loading something else? |
yeah I think its an ld_preload setting the allocator to libtcmalloc |
For future reference, this is probably related to #44242 and #48461 (which was also worked around by unsetting |
Please reopen if still an issue. We may want to check the existence of LD_PRELOAD and LD_LIBRARY_PATH in our build to warn users. |
@ViralBShah I think this is very much still an issue. One of my users ran into this problem (with jemalloc, on a cluster I couldn't access), and it took us forever to diagnose. Some sort of warning would have saved us a lot of time. Unfortunately for this user, just unsetting LD_PRELOAD isn't an option, because he needs to call Julia from another program that does actually need jemalloc. But knowing that earlier would have been very helpful. I'm hoping that building Julia from scratch lets him avoid the problem. 🤞 |
I am not sure how far you'll get with But reopening this issue to have a warning if LD_PRELOAD is set at build or run time. |
Note that |
I was thinking that the message would say something along the lines of: "LD_PRELOAD has been set to $val. If you experience problems with your build or at runtime, please review". |
Also note that julia/stdlib/InteractiveUtils/src/InteractiveUtils.jl Lines 171 to 173 in c6c449c
|
But that does not help if Julia doesn't start at all. |
If Julia doesn't start at all it probably doesn't have any chance to print anything because it dies too early. |
Can we not intercept the signal handler to print a brief something on the C level? |
If there isn't a good option in julia perhaps juliaup could warn? |
Fair enough, but evidently for several cases, Julia does start just fine. In the example I ran into, the error only occurred after Pkg had been loaded and started trying to curl something. |
This was a build of release-1.10.
The same error occurs on my system using juliaup binaries for 1.10, 1.9, and 1.11-rc2
The text was updated successfully, but these errors were encountered: