can we avoid exporting LD_PRELOAD
in set_env_vars.sh
?
#194
Labels
internal-improvement
Refactoring, performance improvement, or other non-breaking change
Category
DRT infrastructure
Describe the feature you'd like to request
Currently,
set_env_vars.sh
sets (exports) a number of environment variables, likeLD_LIBRARY_PATH
,JAVA_HOME
,CLASSPATH
. Most of these are sensible. However, it also sets (exports)LD_PRELOAD
. This is less reasonable in my opinion, because it will cause that preload (Lean'slibm
) to be loaded for every future command in that shell, not just Lean-related ones. (Even worse, at the time of this writing, if yousource set_env_vars.sh
while not havinglean
on yourPATH
, the script will setLD_PRELOAD
to a bogus path, which prints an error message every time you do anything subsequently in that shell. I'll have a PR shortly for the narrow issue of what happens whenlean
is not on yourPATH
.)In my opinion it would be better if we could somehow set
LD_PRELOAD
only for the commands it is necessary, not globally in the shell.Describe alternatives you've considered
Instead of a
set_env_vars.sh
meant for interactive use, we could have a runner script that sets all of these variables just locally (noexport
), and is responsible for calling cargo fuzz.Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: