[erlang-questions] Tracing and debugging
Björn-Egil Dahlberg
egil@REDACTED
Wed Jan 14 18:03:52 CET 2015
On 2015-01-13 14:57, Richard Carlsson wrote:
> What really should be done is that the current interpreting debugger
> should be destroyed with fire and a real bytecode-level debugger
> should be implemented (with low level functionality done in C), which
> would be way faster, only require updating when new Beam operations
> are added, and not require the abstract code to be present in the beam
> files.
Tony Rogvall has written the beginnings of a bytecode interpreter.
See, https://github.com/tonyrog/beam
If someone wanted to build a bytecode interpreter I think that is good
place to start. It does not handle all the opcodes, but a fair amount.
// Björn-Egil
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150114/28b09dbb/attachment.htm>
More information about the erlang-questions
mailing list