[erlang-questions] unhelpful backtrace truncation

Roger Critchlow rec@REDACTED
Tue Dec 9 01:56:14 CET 2008


This kind of truncated stack backtrace, generated by erl -boot start_sasl:

** Reason for termination ==
** {{key_exists,"7b181d15cebb4c86a6ad7fed3dbf30ce2223b4c5"},
    [{gb_trees,insert_1,4},
     {gb_trees,insert_1,4},
     {gb_trees,insert_1,4},
     {gb_trees,insert_1,4},
     {gb_trees,insert_1,4},
     {gb_trees,insert_1,4},
     {gb_trees,insert_1,4},
     {gb_trees,insert_1,4}]}

is not very helpful.

It is especially galling since I had to page past a 4000 line print
out of the server's state to reach it.

Is there some option to start_sasl which would print the entire stack backtrace?

-- rec --



More information about the erlang-questions mailing list