Very strange bug

Vladimir Sekissov <>
Wed Nov 20 11:28:49 CET 2002


Good day,

klacke> Ultra weird ... what's in your .erlang
klacke> 
klacke> does it happen if you start erlang as 
klacke> 
klacke> # /usr/local/bin/yaws -i
klacke> 
klacke> as well ??

My ~/.erlang is clean. I found this problem first time when I'd tried
to start yaws:

$ ./yaws -i

and got and error trying to load demo site.

I'm now starting erl as 'erl -boot start_sasl ....' and haven't any
problem. May be somebody who knows distinction between 'sasl' and
'clean' code loading can clarify the problem.

Best Regards,
Vladimir Sekissov

klacke> On Tue, Nov 19, 2002 at 03:29:44AM +0500, Vladimir Sekissov wrote:
klacke> > Good day,
klacke> > 
klacke> > I've discovered a very strange (for me) bug when I'm starting Erlang
klacke> > with clean boot without sasl.
klacke> > 
klacke> > Lets explain by example:
klacke> > 
klacke> > $ /usr/local/bin/erl
klacke> > 
klacke> > Eshell V5.2  (abort with ^G)
klacke> > 1> m(file).
klacke> > 
klacke> > Module file compiled: Date: October 24 2002, Time: 11.26
klacke> > Compiler options:  [v3,
klacke> >                     debug_info,
klacke> >                     {i,"../include"},
klacke> >                     {outdir,"../ebin"},
klacke> >                     {cwd,"/usr/local/src/otp_src_R9B-0/lib/kernel/src"}]
klacke> > Object file: /usr/local/lib/erlang/lib/kernel-2.8.0/ebin/file.beam
klacke> > Exports: 
klacke> > ... skipped...
klacke> > eval/1                        read/2
klacke> > file_info/1                   read_file/1
klacke> > format_error/1                read_file_info/1
klacke> > ... skipped...
klacke> > 
klacke> > 2> file:read_file("./www/HEAD").
klacke> > {ok, ...}
klacke> > 
klacke> > 3> yaws:start().
klacke> > 
klacke> > =INFO REPORT==== 19-Nov-2002::02:57:09 ===
klacke> > Using config file /home/svg/yaws.conf
klacke> > =INFO REPORT==== 19-Nov-2002::02:57:09 ===
klacke> > Listening to 127.0.0.1:8000 for servers ["localhost:8000"]
klacke> > ok
klacke> > 
klacke> > 4> m(file).
klacke> > ... skipped...
klacke> > eval/1                        rawopen/2
klacke> > file_info/1                   read/2
klacke> > format_error/1                read_file_info/1
klacke> > get_cwd/0                     read_link/1
klacke> > ... skipped...
klacke> > 
klacke> > 5> file:read_file("./www/HEAD").
klacke> > ** exited: {undef,[{file,read_file,
klacke> >                          ["./www/HEAD"]},
klacke> >                    {erl_eval,expr,3},
klacke> >                    {erl_eval,exprs,4},
klacke> >                    {shell,eval_loop,2}]} **
klacke> > 
klacke> > 
klacke> > As you can see in second output of m(file) declaration of read_file/1
klacke> > is absent and function is not available.
klacke> > 
klacke> > When I'm starting Erlang with sasl all is ok.
klacke> > 
klacke> > Can somebody point me to the cause of the problem.
klacke> > 
klacke> > The system is GentooLinux-1.4/GCC-3.1/kernel-2.4.19
klacke> > 
klacke> 
klacke> 
klacke> Ultra weird ... what's in your .erlang
klacke> 
klacke> does it happen if you start erlang as 
klacke> 
klacke> # /usr/local/bin/yaws -i
klacke> 
klacke> as well ??
klacke> 
klacke> 
klacke> /klacke
klacke> 
klacke> -- 
klacke> Claes Wikstrom                        -- Caps lock is nowhere and
klacke> Alteon WebSystems                     -- everything is under control          
klacke> http://www.bluetail.com/~klacke      
klacke> cellphone: +46 70 2097763



More information about the erlang-questions mailing list