GS application

Ulf Wiger <>
Wed Oct 25 11:43:38 CEST 2000


You can do this quite easily by using "erl -boot start_sasl", or even
set this as the default boot script when installing Erlang.

<advanced>
If you build your own boot scripts, all you have to do is of course to
add sasl in the list of applications in your .rel file.
</advanced>

/Uffe

On Wed, 25 Oct 2000, Klacke wrote:

>It can be a bit confusing for newbies with processes that silently crash.
>If we first start sasl ( application:start(sasl) ), and then instead 
>of spawn call, proc_lib:spaw/3, we get a nice error printout on the tty.
>
>=CRASH REPORT==== 25-Oct-2000::11:33:59 ===
>  crasher:
>    pid: <0.61.0>
>    registered_name: []
>    error_info: {undef,[{gs,draw_line,
>                             [{7,<0.31.0>},
>                              solid,
>                              2,
>                              [{10,50},{30,50},{30,60},{60,60}]]},
>                         {line2,internal,0},
>                         {proc_lib,init_p,5}]}
>    initial_call: {line2,internal,[]}
>    ancestors: [<0.22.0>]
>    messages: []
>    links: [<0.31.0>]
>    dictionary: []
>    trap_exit: false
>    status: running
>    heap_size: 377
>    stack_size: 21
>    reductions: 120
>  neighbours:
>
>
>Then it's pretty clear what goes on.
>
>/klacke


-- 
Ulf Wiger                                    tfn: +46  8 719 81 95
Strategic Product & System Management        mob: +46 70 519 81 95
Ericsson Telecom AB,              Datacom Networks and IP Services
Varuvägen 9, Älvsjö,                    S-126 25 Stockholm, Sweden




More information about the erlang-questions mailing list