Very strange behaviour!

[Chandrashekhar Mullaparthi]

There is a -init_debug option for erl - it works with werl as well.

chandru: /export/home/chandru 501>erl -init_debug
{progress,preloaded}
{progress,kernel_load_completed}
{progress,modules_loaded}
{start,heart}
{start,error_logger}
{start,application_controller}
{progress,init_kernel_started}
{apply,{application,load,[{application,stdlib,[{description,"ERTS  CXC 138
10"},{vsn,"1.11.3"},{id,[]},{modules,[beam_lib,c,calendar,dets,dets_server,d
ets_sup,dets_utils,dets_v8,dets_v9,dict,digraph,digraph_utils,edlin,epp,eval
_bits,erl_bits,erl_compile,erl_eval,erl_id_trans,erl_internal,erl_lint,erl_p
arse,erl_posix_msg,erl_pp,erl_scan,erl_tar,error_logger_file_h,error_logger_
tty_h,ets,file_sorter,filelib,filename,gb_trees,gb_sets,gen,gen_event,gen_fs
m,gen_server,io,io_lib,io_lib_format,io_lib_fread,io_lib_pretty,lib,lists,li
sts_sort,log_mf_h,math,ms_transform,orddict,ordsets,otp_internal,pg,pool,pro
c_lib,proplists,queue,random,regexp,sets,shell,shell_default,slave,sofs,stri
ng,supervisor,supervisor_bridge,sys,timer,vector,win32reg]},{registered,[tim
er_server,rsh_starter,take_over_monitor,pool_master,dets]},{applications,[ke
rnel]},{included_applications,[]},{env,[]},{start_phases,undefined},{maxT,in
finity},{maxP,infinity}]}]}}
{apply,{application,load,[{application,sasl,[{description,"SASL  CXC 138
11"},{vsn,"1.9.4"},{id,[]},{modules,[sasl,alarm_handler,format_lib_supp,misc
_supp,otp_mib,overload,rb,rb_format_supp,release_handler,release_handler_1,e
rlsrv,sasl_report,sasl_report_tty_h,sasl_report_file_h,systools,systools_mak
e,systools_rc,systools_relup,systools_lib]},{registered,[sasl_sup,alarm_hand
ler,overload,release_handler]},{applications,[kernel,stdlib]},{included_appl
ications,[]},{env,[{sasl_error_logger,tty},{errlog_type,all}]},{start_phases
,undefined},{maxT,infinity},{maxP,infinity},{mod,{sasl,[]}}]}]}}
{progress,applications_loaded}
{apply,{application,start_boot,[kernel,permanent]}}
Erlang (BEAM) emulator version 5.2.2 [hipe] [threads:0]

{apply,{application,start_boot,[stdlib,permanent]}}
Eshell V5.2.2  (abort with ^G)
1> {apply,{application,start_boot,[sasl,permanent]}}

=PROGRESS REPORT==== 23-May-2003::15:29:45 ===
          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.33.0>},
                       {name,alarm_handler},
                       {mfa,{alarm_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 23-May-2003::15:29:45 ===
          supervisor: {local,sasl_safe_sup}
             started: [{pid,<0.34.0>},
                       {name,overload},
                       {mfa,{overload,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]

=PROGRESS REPORT==== 23-May-2003::15:29:45 ===
          supervisor: {local,sasl_sup}
             started: [{pid,<0.32.0>},
                       {name,sasl_safe_sup},
                       {mfa,{supervisor,
                                start_link,
                                [{local,sasl_safe_sup},sasl,safe]}},
                       {restart_type,permanent},
                       {shutdown,infinity},
                       {child_type,supervisor}]

=PROGRESS REPORT==== 23-May-2003::15:29:46 ===
          supervisor: {local,sasl_sup}
             started: [{pid,<0.35.0>},
                       {name,release_handler},
                       {mfa,{release_handler,start_link,[]}},
                       {restart_type,permanent},
                       {shutdown,2000},
                       {child_type,worker}]
{apply,{c,erlangrc,[]}}

=PROGRESS REPORT==== 23-May-2003::15:29:46 ===
         application: sasl
          started_at: nonode@REDACTED
{progress,started}


-----Original Message-----
From: Chris Pressey [mailto:cpressey@REDACTED]
Sent: 23 May 2003 02:50
To: Vlad Dumitrescu
Cc: erlang-questions@REDACTED
Subject: Re: Very strange behaviour!


On Thu, 22 May 2003 10:14:02 +0200
"Vlad Dumitrescu" <vlad_dumitrescu@REDACTED> wrote:

> Solved!!!
> 
> > - or just littering the startup code with erlang:display("here!")
> >   statements... crude but at least an indication of roughly where
> >   the slowdown is occurring
> 
> Thanks a lot for the idea! I was so frustrated that I couldn't think
> straight! :-)

Glad I could help :)  Especially since I generally have no idea what I'm
doing... :)

Mini-poll question to the list in general:

What would you think of a -verbose_startup option for helping debug
these sorts of problems?

-Chris



 NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.