Errors in Erlang

Lennart Ohman <>
Mon Apr 17 18:23:13 CEST 2006


Hi,
since your application stops "spontainously" (that is you
do not call application:stop/1), the answer is somewhere in
your supervisor structure spanning the processes belonging
to it.

My first suggestion is that you make sure you have the
sasl application running before starting your own application.
In that way you will get supervisor reports on what actually
starts and where it goes wrong.

Best regards,
Lennart

-------------------------------------------------------------
Lennart Ohman                   office  : +46-8-587 623 27
Sjoland & Thyselius Telecom AB  cellular: +46-70-552 67 35
Sehlstedtsgatan 6               fax     : +46-8-667 82 30
SE-115 28, STOCKHOLM, SWEDEN    email   : 
> -----Original Message-----
> From:  [mailto:owner-erlang-
> ] On Behalf Of Pupeno
> Sent: Monday, April 17, 2006 3:51 PM
> To: 
> Subject: Errors in Erlang
> 
> Hello,
> I tend to have a problem in Erlang. Most runtime errors doesn't give any
> clues
> about what happened. I run application:start(fanterlasticfour). and all I
> get
> is:
> 
> =INFO REPORT==== 17-Apr-2006::13:32:43 ===
>     application: fanterlasticfour
>     exited: {shutdown,{fanterlasticfour_app,start,[normal,[]]}}
>     type: temporary
> {error,{shutdown,{fanterlasticfour_app,start,[normal,[]]}}}
> 
> it didn't start, but I have no idea where or why it died. How do you
> proceed
> when you have something like this ? Or how do I avoid it ?
> Thank you.
> --
> Pupeno <> (http://pupeno.com)





More information about the erlang-questions mailing list