Different stacktrace results

[peerreynders]

http://erlang.org/doc/man/erlang.html#ghlink-get_stacktrace-0-id296073

erlang:get_stacktrace/0 is deprecated and will stop working in a future release.

http://erlang.org/doc/man/erlang.html#ghlink-process_info-2-id315061

{current_stacktrace, Stack}

Returns the current call stack back-trace ( stacktrace ) of the process. The stack has the same format as returned by erlang:get_stacktrace/0. The depth of the stacktrace is truncated according to the backtrace_depth system flag setting.

Also given “last call optimization” stack traces are a bit different.

How does a try/rescue on a recursive function call affect the stack?

It’s actually not Observer’s fault - it is just displaying what it is getting back from process_info. {current_stacktrace, Stack} Returns the current call stack back-trace (stacktrace) of the process. The stack has the same format as returned by erlang:get_stacktrace/0. The depth of the stacktrace is truncated according to the backtrace_depth system flag setting. Seems the default setting for backtrace_depth is 8 and once you increase its length it is allowed to grow further - though even t…