You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
When Lumen raises badarity and it is passed through a monitor, it has Info as {badarity, {Fun, Args}}, but it is supposed to be {{badarity, {Fun, Args}}, Stacktrace}. I believe this is the case because when badarity happens it counts as exit reason, which is always {reason, stacktrace}.
{parent,badarity}
ok
=ERROR REPORT==== 24-Aug-2020::11:52:33.289409 ===
Error in process <0.146.0> with exit value:
{{badarity,{#Fun<start.1.105435764>,[]}},[{erlang,apply,2,[]}]}
Difference with exit/1
It should be noted that exit(reason) DOES NOT include the stack trace and so counts whatever is passed to exit/1 as the "exit reason"
Commands
erl
catch exit(reason)
Output
{'EXIT', reason}
The text was updated successfully, but these errors were encountered:
When Lumen raises
badarity
and it is passed through a monitor, it hasInfo
as{badarity, {Fun, Args}}
, but it is supposed to be{{badarity, {Fun, Args}}, Stacktrace}
. I believe this is the case because when badarity happens it counts as exit reason, which is always{reason, stacktrace}
.Lumen
init.erl
BEAM
start.erl
Commands
erl
c(start).
start:start().
Output
Difference with
exit/1
It should be noted that
exit(reason)
DOES NOT include the stack trace and so counts whatever is passed toexit/1
as the "exit reason"Commands
erl
catch exit(reason)
Output
The text was updated successfully, but these errors were encountered: