Lukas Backström

> Personally not a fan of so many comments in a template. Comments are great if it is the first time you see a template, but when it is the...

> OTP team might change their build system to bundle the docs in EEP 48 format - it would benefit not just Erlang, but Elixir, LFE, Efene, and Alpaca users,...

@lackac We would appreciate any help you can give. The way I imagine it working is to basically take a copy of the xslt rules used to generate the man...

I created an issue here https://bugs.erlang.org/browse/ERL-708 for further discussion. Feel free to chime in. Regarding the format, one thing that I think is important is to have the same format...

The [edoc PR](https://github.com/erlang/otp/pull/2803) for EEP-48 is nearing completion. It includes documentation about how to configure rebar3 to generate chunks by calling `rebar3 edoc`. In the long run, do we want...

hmm, I think it is code:get_object_code/1 that is the culprit [here](https://github.com/erlang-ls/erlang_ls/blob/main/apps/els_dap/src/els_dap_general_provider.erl#L576). There may be something we can do about it. I will check and see.

[We](http://erlang.org) use the jit-reader support in gdb to do stack unwinding and symbol resolution. It works well enough and we found it easier to work with than elf and dwarf.

Seems like you need something more complex than what we needed. We use this as the jit-reader code: https://github.com/erlang/otp/blob/master/erts/etc/unix/jit-reader.c And the data is generated here: https://github.com/erlang/otp/blob/master/erts/emulator/beam/jit/beam_asm.cpp#L575

Thanks!

No news yet. We are planning to do this at some point, but have not gotten around to it yet.