[erlang-bugs] erlang module not in sticky dir?

Loïc Hoguin essen@REDACTED
Thu May 8 14:01:09 CEST 2014


There's also this which is just odd.

essen@REDACTED (20) % erl
Erlang/OTP 17 [erts-6.0] [source] [64-bit] [smp:4:4] [async-threads:10] 
[hipe] [kernel-poll:false]

Eshell V6.0  (abort with ^G)
1> erlang:function_exported(erlang, apply, 3).
true
2> erlang:function_exported(erlang, is_map, 1).
false
3> erlang:function_exported(erlang, is_list, 1).
false

On 05/08/2014 11:59 AM, Stavros Aronis wrote:
> Somewhat related (posted earlier at
> http://erlang.org/pipermail/erlang-bugs/2014-April/004300.html )
>
> $ erl
> Erlang/OTP 17 [erts-6.0] [source-07b8f44] [64-bit] [smp:8:8]
> [async-threads:10] [hipe] [kernel-poll:false]
>
> Eshell V6.0  (abort with ^G)
> 1> erlang:is_builtin(erlang,apply,3).
> false
>
> Regards,
>
> Stavros
>
>
> On Thu, May 8, 2014 at 10:58 AM, Siri Hansen <erlangsiri@REDACTED
> <mailto:erlangsiri@REDACTED>> wrote:
>
>     Thanks for reporting! I have written a ticket for this.
>     Regards
>     /siri
>
>
>     2014-04-26 21:00 GMT+02:00 Loïc Hoguin <essen@REDACTED
>     <mailto:essen@REDACTED>>:
>
>         A user got confused by pretty much this:
>
>         % erl
>         Erlang/OTP 17 [erts-6.0] [source] [64-bit] [smp:4:4]
>         [async-threads:10] [hipe] [kernel-poll:false]
>
>         Eshell V6.0  (abort with ^G)
>         1> l(erlang).
>         {module,erlang}
>         2> l(gen_server).
>         {error,sticky_directory}
>         3>
>         =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 application: https://github.com/rustyio/__sync
>         <https://github.com/rustyio/sync>
>
>         Details are not important. I suggest however making the
>         preloaded Erlang modules be sticky by default to prevent awkward
>         behavior such as this.
>
>         --
>         Loïc Hoguin
>         http://ninenines.eu
>         _________________________________________________
>         erlang-bugs mailing list
>         erlang-bugs@REDACTED <mailto:erlang-bugs@REDACTED>
>         http://erlang.org/mailman/__listinfo/erlang-bugs
>         <http://erlang.org/mailman/listinfo/erlang-bugs>
>
>
>
>     _______________________________________________
>     erlang-bugs mailing list
>     erlang-bugs@REDACTED <mailto:erlang-bugs@REDACTED>
>     http://erlang.org/mailman/listinfo/erlang-bugs
>
>

-- 
Loïc Hoguin
http://ninenines.eu



More information about the erlang-bugs mailing list