[erlang-questions] unhelpful backtrace truncation

[Roger Critchlow]

No, I get the same backtrace with erlang:system_flag(backtrace_depth,
100) as I did before.

Thanks for the suggestion.

-- rec --

On Tue, Dec 9, 2008 at 4:45 PM,  <michael.truog@REDACTED> wrote:
> Wouldn't the function call "erlang:system_flag(bracktrace_depth, Depth)"
> provide you more information here?
>
>
> -----Original Message-----
> From: erlang-questions-bounces@REDACTED
> [mailto:erlang-questions-bounces@REDACTED] On Behalf Of ext Roger
> Critchlow
> Sent: Monday, December 08, 2008 4:56 PM
> To: Erlang-Questions (E-mail)
> Subject: [erlang-questions] unhelpful backtrace truncation
>
> 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 --
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>