Folsom supervisor dies everytime ErlangVM gets any exception/error #17

ztmr opened this Issue Apr 24, 2012 · 3 comments

3 participants


I think this should not happen:

tmr@gersemi:~/src/tmp/folsom$ erl -pa deps/bear/ebin -pa ebin -sname foo
Erlang R15B (erts-5.9) [source] [64-bit] [smp:8:8] [async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.9  (abort with ^G)
(foo@gersemi)1> folsom_sup:start_link ().
(foo@gersemi)2> a=b.
** exception error: no match of right hand side value b
=ERROR REPORT==== 24-Apr-2012::22:26:46 ===
** Generic server folsom_sup terminating 
** Last message in was {'EXIT',<0.40.0>,{{badmatch,b},[{erl_eval,expr,3,[]}]}}
** When Server state == {state,
** Reason for termination == 
** {{badmatch,b},[{erl_eval,expr,3,[]}]}


Am I doing something wrong?



Well, calling folsom_sup:start_link() will link folsom to your shell process, so it will die when your shell does. It's probably wrong for folsom:start/0 to call start_link when it actually shouldn't be linked.

I'm going to submit a pull request soon that lets you start folsom in a more sensible way using application:start(folsom), where it won't die when your shell does.


See #18 - this would basically fix your issue, although you would want to start calling folsom:start() instead of folsom_sup:start_link().


Per Bob's PR this is fixed.

@joewilliams joewilliams closed this May 1, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment