[erlang-questions] Subtle behaviour of Erlang scheduler

[KatolaZ]

On Fri, May 25, 2007 at 04:45:07PM +0200, Ulf Wiger (TN/EAB) wrote:
> 
> Actually, c() does load the new module.
> 
> From c.erl in stdlib:
> 
> c(File, Opts0) when list(Opts0) ->
>     Opts = [report_errors,report_warnings|Opts0],
>     case compile:file(File, Opts) of
>         {ok,Mod} ->                             %Listing file.
>             machine_load(Mod, File, Opts);
>         {ok,Mod,_Ws} ->                         %Warnings maybe turned
> on.
>             machine_load(Mod, File, Opts);
>         Other ->                                %Errors go here
>             Other
>     end; 
> 
> BR,
> Ulf W
> 

So, Ulf, do you or anybody else have any idea about this strange
behaviour of erl scheduler ??? I hope someone can say if we hit a
big-bug in the priority management system, and what it the cause.

HND

Enzo

-- 
[ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ]
[ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ]
[ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ]
[ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ]