otp.git/lib/debugger/test/int_eval_SUITE_data/stacktrace.erl, branch OTP-21.1.4 Mirror of Erlang/OTP repository. emulator: Add a fourth element in exception stacktraces 2011-08-16T06:58:50+00:00 Björn Gustavsson bjorn@erlang.org 2011-02-16T05:54:15+00:00 be04820c070d01d7565b936fa14efc2941055e0b This commit is a preparation for introducing location information (filename/line number) in stacktraces in exceptions. Currently a stack trace looks like: [{Mod1,Function1,Arity1}, . . . {ModN,FunctionN,ArityN}] Add a forth element to each tuple that can be used indication the filename and line number of the source file: [{Mod1,Function1,Arity1,Location1}, . . . {ModN,FunctionN,ArityN,LocationN}] In this commit, the fourth element will just be an empty list, and we will change all code that look at or manipulate stacktraces. 
This commit is a preparation for introducing location information
(filename/line number) in stacktraces in exceptions. Currently
a stack trace looks like:

  [{Mod1,Function1,Arity1},
   .
   .
   .
   {ModN,FunctionN,ArityN}]

Add a forth element to each tuple that can be used indication
the filename and line number of the source file:

  [{Mod1,Function1,Arity1,Location1},
   .
   .
   .
   {ModN,FunctionN,ArityN,LocationN}]

In this commit, the fourth element will just be an empty list,
and we will change all code that look at or manipulate stacktraces.
Don't include tail-recursive calls in stacktraces 2011-08-16T06:58:48+00:00 Björn Gustavsson bjorn@erlang.org 2011-03-31T06:40:36+00:00 d6dc673a00f6244b03e1e9c849e3267b141c23c7 The stacktrace in debugger-generated exceptions should be as similar to stacktraces in BEAM-generated exceptions as possible. 
The stacktrace in debugger-generated exceptions should be
as similar to stacktraces in BEAM-generated exceptions as
possible.