Migrate dbg and etop to use trace sessions

[garazdawi]

This PR moves all dbg functionality to use a trace session instead of relying on the global session.

In addition it also adds a a new dbg:session/1,2 API that can be used to create new dbg session that are isolated from eachother.

As a proof of concept the etop application has been converted to use the new sessions so that it now is possible to run multiple etop and dbg at the same time in a system without them interfeering with eachother.

[github-actions]

CT Test Results

    6 files    211 suites   2h 0m 18s ⏱️
3 106 tests 2 803 ✅ 302 💤 1 ❌
4 072 runs  3 693 ✅ 378 💤 1 ❌

For more details on these failures, see this check.

Results for commit 4aee35a.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• Windows Installer

// Erlang/OTP Github Action Bot

[essen]

How does a dbg session differ from a dbg tracer?

[garazdawi]

Not much, except that you can have many of them. The API is not set in stone. Ideas are very welcome on how to do it.

[sverker]

I don't think this will work as trace:process will not accept *ports atoms and trace:port will not accept *processes atoms. Maybe they should silently ignore such atoms?

[garazdawi]

Calling trace:process(S, all, true, [ports]) works, but returns 0, so it seems to already today be ignored?

[sverker]

I mean these will currently fail:

trace:process(S, ports, ...).
trace:process(S, new_ports, ...).
trace:process(S, existing_ports, ...).
trace:port(S, processes, ...).
trace:port(S, new_processess, ...).
trace:port(S, existing_processes, ...).