Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-04-05 | Use erlang:demonitor(Ref, [flush]) where applicable | Loïc Hoguin | |
2013-01-10 | debugger: Fix user evalution dependent of bindings in trace window | Dan Gudmundsson | |
Bindings in erl_eval is an orddict and must be sorted otherwise they are not found, depending on creation order | |||
2011-12-09 | Update copyright years | Björn-Egil Dahlberg | |
2011-08-16 | emulator: Add a fourth element in exception stacktraces | Björn Gustavsson | |
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. | |||
2011-08-16 | Don't build stacktrace until erlang:get_stacktrace() is called | Björn Gustavsson | |
Currently, dbg_istk:exception_stacktrace/2 does not do a very good job imitating BEAM's stacktrace. The reason is that it need to be relatively fast since a simulated stacktrace is constructed not only when an exception oocurs, but also before every call to non-interpreted code. To prepare for a future more thorough (and slower) stacktrace construction, refactor the building of the stacktrace so that it only is done when erlang:get_stacktrace/0 is called. | |||
2010-09-10 | Remove warnings for clashes with new autoimported BIFs | Patrik Nyblom | |
2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |