Debugging crashes during init

Emil Hellman emil.hellman@REDACTED
Tue Sep 27 19:44:02 CEST 2005


I'm no expert on erlang applications, but have you tried starting the
application with application:start(<Name of your Application>)? If you
are not certain where the application acctually crashes you could try
starting the toplevel supervisor by hand and see if everything works
as intended...If it doesn't work you will most likely get better crash
reports, but if it does work you know that the crash has something to
do with your module implementing the application behaviour (which you
are implying). Also you could try starting up the sasl application
before starting your own application (if you're not doing that
already)... that might give you some aditional output i suppose...
Then again I might be off base here since I'm still just a student at
uni =)


On 9/27/05, Tim Bates <tim@REDACTED> wrote:
> Hi folks,
> When a process crashes during normal operation I get a lovely error
> report printout with a reason for the crash and a traceback. When
> something crashes inside my Application:start/2 functions I get this:
> $ erl -boot lib/traderl/priv/traderl -config test -traderl gainfiles
> '[test1.csv, test2.csv]'
> Erlang (BEAM) emulator version 5.4.8 [source] [hipe] [threads:0]
> =INFO REPORT==== 27-Sep-2005::20:50:40 ===
>      application: traderl
>      exited: {shutdown,{traderl_app,start,[normal,[]]}}
>      type: permanent
> {"Kernel pid terminated",application_controller,shutdown}
> Crash dump was written to: erl_crash.dump
> Kernel pid terminated (application_controller) (shutdown)
> The crash dump doesn't really give me any more useful information than
> this. How can I find out where and why my init routines crashed? I've
> been reduced to using print statements and it's frustrating to say the
> least.
> Thanks,
> Tim.
> --
> Tim Bates

More information about the erlang-questions mailing list