[erlang-bugs] erlang module not in sticky dir?
Sat Apr 26 21:00:15 CEST 2014
A user got confused by pretty much this:
Erlang/OTP 17 [erts-6.0] [source] [64-bit] [smp:4:4] [async-threads:10]
Eshell V6.0 (abort with ^G)
=ERROR REPORT==== 26-Apr-2014::20:56:37 ===
Can't load module that resides in sticky dir
For some reasons his erlang:apply/3 ended up not being a BIF anymore and
instead called erlang:apply/3 in a loop because the file contains:
apply(Mod, Name, Args) ->
erlang:apply(Mod, Name, Args).
The file had been recompiled and reloaded automatically using the sync
Details are not important. I suggest however making the preloaded Erlang
modules be sticky by default to prevent awkward behavior such as this.
More information about the erlang-bugs